[bugfix] Added APOptions []int in client.GSSAPIBindRequest(...) and client.InitSecContext(...), fixes #536 #537
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixing Kerberos authentication due to missing APOption "MutualRequired"
Overview of the fix
In
client.InitSecContext(...)
I have changed the
client.InitSecContext(...)
prototype from:to:
to be able to pass specific flags through the
APOptions []int
to the call tospnego.NewKRB5TokenAPREQ(client.Client, tkt, ekey, gssapiFlags, APOptions)
In
client.GSSAPIBind(...)
I have left this function as it was, so it can be used in the generic case of GSSAPI authentication without the need to pass specific AP Options flags in parameters.
In
client.GSSAPIBindRequest(...)
I have changed the
client.GSSAPIBindRequest(...)
prototype from:to
Example of a working code for Kerberos authentication
Summary
These
APOptions []int
can now be set when callingclient.GSSAPIBindRequest(...)
, which will then pass it to the underlyingclient.InitSecContext(...)
, which will then be processed in the call tospnego.NewKRB5TokenAPREQ(client.Client, tkt, ekey, gssapiFlags, APOptions)
Best Regards,