-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
ISSUE-603: Minor: Registry is failing to parse the doAs user #604
Conversation
Please merge to CSP-3.0 as well. |
@@ -461,8 +461,8 @@ protected static String getDoasUser(HttpServletRequest request) { | |||
if (doAsUser.isEmpty()) { | |||
return null; | |||
} | |||
break; |
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.
@guruchai : Will there be multiple "doAs" keys in the header ?
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.
@raju-saravanan It's query parameter, not header.
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.
@guruchai So multiple "doAs" query parameter ? Can you tell when there would be multiple "doAs" query parameters ?
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, with regards to the question, it does not make sense to have multiple doAs query parameters. Since the doAs is typically attached by a proxy server, it makes sense to pick the last one.
So break statement does not make sense. Thanks for pointing!
@raju-saravanan Can you check? |
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.
@guruchai Thanks for this PR. +1 LGTM.
Fixes #603