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
Bug 1541461 - Deal with buggy encoded scopes from service catalog. #754
Conversation
| switch { | ||
| case ok && userInfo.Scopes != nil: | ||
| log.Infof("Unable to determine correct scope to use. Found both top level scope and scope in extras.") | ||
| return false, http.StatusForbidden, fmt.Errorf("unable to determine correct scope to use") |
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.
@shawn-hurley how likely is this situation? Will we get into a situation where we're screwed and always getting forbidden? What would cause both information to come in?
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.
I have a question, but the code looks good.
|
I believe the situation would not occur with just the service catalog. I
believe this is just to be very explicit about what would happen if it did.
There is no version of the service catalog this should happen on.
…On Mon, Feb 12, 2018 at 5:26 PM Jesus Rodriguez ***@***.***> wrote:
***@***.**** approved this pull request.
I have a question, but the code looks good.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#754 (review)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABza98Ykc-m74v9lj7gIlGgbxq4SNX1Bks5tULqggaJpZM4SCnMJ>
.
|
|
@shawn-hurley okay, ACK! |
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.
ACK
Describe what this PR does and why we need it:
Will allow us to handle scope that has been incorrectly encoded
Changes proposed in this pull request