set resourceOwner services directly without using tag #1874
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
dmaicher
force-pushed
the
fix-issue-1873
branch
from
0a6f6aa
to
42ed6e9
Compare
dmaicher
force-pushed
the
fix-issue-1873
branch
from
42ed6e9
to
e643a20
Compare
stloyd
reviewed
Jan 10, 2022
|
I would like to have custom oauth resource in functional test to prove this really fixes your problem from #1873 |
Sure. Let me look into it. |
dmaicher
commented
Jan 10, 2022
stloyd
approved these changes
Jan 10, 2022
|
Thanks @dmaicher ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I don't think we need the tag
hwi_oauth.resource_owner. Registering the service locator ourselves seems straightforward and fixes #1873