New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ELY-1150] - Revisit branches in handleOne method in ServerAuthenticationContext.createCallbackHandler() #862
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you sure this is needed? I think in some cases it was a deliberate decision that once this callback has been handled we should handle no more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The CachedIdentityAuthorizeCallback branch still looks wrong to me. I don't think it should be returning, since that would prevent handling subsequent callbacks.
@@ -1031,6 +1034,7 @@ private void handleOne(final Callback[] callbacks, final int idx) throws IOExcep | |||
log.tracef("Handling CachedIdentityAuthorizeCallback: principal = %s authorizedIdentity = %s", principal, authorizedIdentity); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Three lines before this one is a return
statement. Should it instead be a handleOne()/continue? And there's another as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry,it is wrong. It should go in the finally block where AI is set.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dmlloyd I've removed the try/finally block and return statements. In case an exception is thrown we should not call handleOne
.
@darranl I can't remember any reason for not calling |
94d6cad
to
d0ca39f
Compare
…tionContext.createCallbackHandler()
No description provided.