-
Notifications
You must be signed in to change notification settings - Fork 10.4k
RC1 Port: Add FailureReasons (#35425) #35529
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
Conversation
@wtgodbe so there is modification to unshipped APIs in this PR, but I don't think I've modified any public shipped apis, this was just a cherry pick of a main PR, so I'm not sure how to resolve the code check failure, any ideas? |
@BrennanConroy fixed that check yesterday, it should pass now |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
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.
Is it possible to create the failure list only if it's needed?
src/Security/Authorization/Core/src/AuthorizationHandlerContext.cs
Outdated
Show resolved
Hide resolved
src/Security/Authorization/Core/src/AuthorizationHandlerContext.cs
Outdated
Show resolved
Hide resolved
src/Security/Authorization/Core/src/AuthorizationFailureReason.cs
Outdated
Show resolved
Hide resolved
src/Security/Authorization/Core/src/AuthorizationFailureReason.cs
Outdated
Show resolved
Hide resolved
This comment has been minimized.
This comment has been minimized.
src/Security/Authorization/Core/src/AuthorizationHandlerContext.cs
Outdated
Show resolved
Hide resolved
Co-authored-by: Kahbazi <[email protected]>
src/Security/Authorization/Core/src/AuthorizationHandlerContext.cs
Outdated
Show resolved
Hide resolved
src/Security/Authorization/Core/src/AuthorizationHandlerContext.cs
Outdated
Show resolved
Hide resolved
…t.cs Co-authored-by: Kahbazi <[email protected]>
Ah! failed again! I hope this would fix it! @Tratcher #35529 (comment) |
…t.cs Co-authored-by: Kahbazi <[email protected]>
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@wtgodbe ready to merge. |
Resolved as part of #35632. |
Do we need to apply the changes from this PR to main? |
I'm on it! |
Hi @Kahbazi. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context. |
Backport of #35425
Customer Impact
There currently is no way to flow more detailed authorization failures from the IAuthorizationHandler to consumers that are responsible for displaying authorization errors. This change allows handlers to flow custom messages and state
Testing
Automated tests and a new sample demonstrating the usage
Risk
Low