feat: support different jwt scope claim strategies#3531
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3531 +/- ##
==========================================
- Coverage 76.64% 76.62% -0.02%
==========================================
Files 129 129
Lines 9630 9640 +10
==========================================
+ Hits 7381 7387 +6
- Misses 1748 1751 +3
- Partials 501 502 +1
|
aeneasr
left a comment
aeneasr
left a comment
There was a problem hiding this comment.
Awesome, thank you! 🎉 Your contribution makes Ory better :)
aeneasr
force-pushed
the
feat/jwt-scope-claim-strategy
branch
from
d587c93 to
3c986de
Compare
|
Hello @brett-patterson Let me know if I can support you in adding something to the documentation. I have never used the feature so I would need some rough pointers/drafts. Thanks! |
|
Hi there! I have a question for the Ory guys: is this feature already a part of any release? If yes, which one? If no, when should we expect it? |
4 participants
Adds a
strategies.jwt.scope_claimoptional configuration property that controls how the scope claim is represented in JWT access tokens. It can be set to one oflist,string, orboth.list(the default behavior) matches the current behavior of using ascpclaim that is an array of strings.stringuses ascopeclaim as defined in this RFC, a single space-delimited string.bothwill include both thescpandscopeclaim in the token.Related issue(s)
#3524
Checklist
introduces a new feature.
contributing code guidelines.
vulnerability. If this pull request addresses a security vulnerability, I
confirm that I got the approval (please contact
[email protected]) from the maintainers to push
the changes.
works.
Further Comments
These different scope claim strategies were already available in
fosite, this PR is just exposing them through a Hydra configuration property. Open to suggestions on configuration property naming! Will update docs but wanted to get this PR settled first to know what to add to the docs.