-
Notifications
You must be signed in to change notification settings - Fork 205
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
port auth middleware "test client" for user tokens #12929
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
S11001001
added
team/ledger-clients
Related to the Ledger Clients team's components.
component/auth-middleware
concern/testing
labels
Feb 15, 2022
…uth2-test-server-tests-user-tokens
CHANGELOG_BEGIN CHANGELOG_END
A little review of the components:
|
S11001001
requested review from
stefanobaghino-da and
ray-roestenburg-da
as code owners
February 17, 2022 17:48
ray-roestenburg-da
approved these changes
Feb 17, 2022
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.
LGTM
This was referenced Feb 17, 2022
S11001001
added a commit
that referenced
this pull request
Feb 22, 2022
TestMiddlewareUserToken now uses user tokens from the oauth server as well, courtesy #12929. TestMiddlewareClaimsToken is the only middleware-only (non-Client) test that switches the oauth test server back to producing claims tokens, and contains all the tests that depend on claims token semantics. These tests are in a sense exercising the oauth server rather than the middleware. The token returned by the oauth server is irrelevant for the behavior these tests are exercising, so they are merely ported to always run on user tokens. - CallbackUriOverride - LimitedCallbackStore - ClientLimitedCallbackStore - ClientNoRedirectToLogin - ClientYesRedirectToLogin - ClientAutoRedirectToLogin CHANGELOG_BEGIN CHANGELOG_END
garyverhaegen-da
added a commit
that referenced
this pull request
Feb 22, 2022
Merged
7 tasks
S11001001
added a commit
that referenced
this pull request
Feb 24, 2022
Duplicates the trigger service's auth tests for the two modes of the oauth test server from #12929, then selects out the claim-token-dependent tests as explained in #12831 (comment) Part of #12831. * also suppress claims-only tests in oracle-with-oauth2-test * use inClaims for several tests CHANGELOG_BEGIN CHANGELOG_END
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
component/auth-middleware
concern/testing
team/ledger-clients
Related to the Ledger Clients team's components.
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.
Fixes #12881 by making the oauth2 test server invent user tokens instead of claim tokens if you ask it to. As with the claim tokens, these aren't "real" tokens backed by a participant server, so only a subset of the tests makes sense, and we abstract over the shared compatible tests accordingly.
Pull Request Checklist
CHANGELOG_BEGIN
andCHANGELOG_END
tagsNOTE: CI is not automatically run on non-members pull-requests for security
reasons. The reviewer will have to comment with
/AzurePipelines run
totrigger the build.