Travis Bischel

I'm going to go ahead and close this for now, I'm not sure of a better way to do this, and I think the documentation should help :)

Can you try setting the `PersistAfterAuth` option to true?

I think it may be good if I automatically set that to true in `AsMechanism`, basically what I think is happening is that after the first authentication, the client is...

EOF would be the server closing the connection unexpectedly connection for some reason. I think it is eventually retried, but I’m not sure why the server is closing the cxn—something...

It wont leak goroutines. The key lines are here: https://github.com/twmb/franz-go/blob/514f3638dbf5e74cfdcfdca4e93f7e04b9fcf1ac/pkg/sasl/kerberos/kerberos.go#L65-L72 Basically, this code will always return your same original input client. By persisting after authorization, the sasl flow will avoid...

Scratch that reply, sorry I misread what you linked to in my email. Yes, each call there will leak a kerberos client, which will leak a goroutine. I can think...

I think what I'll do: * add a new field to Opt, `ClientFn`, if that is non-nil, use it. * add an optional interface that destroys a sasl, check this...

I think I can implement some of this internally with a 1.6.1 patch -- specifically the second point -- and a new minor version of the kerberos dep.

(deleted two comments above now that the original issue has been diagnosed just in case they have some inadvertent auth in the logs)

The features have now been released, please check out the commits just above, this is in pkg/sasl/kerberos v1.1.0: ``` go get github.com/twmb/franz-go/pkg/sasl/[email protected] ``` You will want to change to using...