The most scalable and customizable OpenID Certified™ OpenID Connect and OAuth Provider on the market. Become an OpenID Connect and OAuth2 Provider over night. Broad support for related RFCs. Written in Go, cloud native, headless, API-first. Available as a service on Ory Network and for self-hosters.
I want to implement a scope strategy in my Application which allows for different separators between dynamic scopes, resources & verbs. Right now this is the closest we can get.
Describe your ideal solution
The ideal solution would be to follow this recommendation.
For summary we'd have these things to check for:
- for prefix scopes so budget-* matches budget-400 and budget-5
: to separate resources so right now hydra.clients would be replaced by hydra:clients
. for specifying the permission/verb hydra:clients.read for example
Workarounds or alternatives
I would have to use . as separator exclusively, making it hard to differentiate between prefix, resource and verb in my application.
Or I'd need to compile my own fosite & hydra with my custom scope strategy which adds significant complexity to my deployment pipeline & maintenance.
Version
latest
Additional Context
I'd also be happy if I could just use the prefix scopes and continue to use . as resource as well as verb separator.
zoop-btc
commented
6 months ago
Preflight checklist
Ory Network Project
No response
Describe your problem
I want to implement a scope strategy in my Application which allows for different separators between dynamic scopes, resources & verbs. Right now this is the closest we can get.
Describe your ideal solution
The ideal solution would be to follow this recommendation. For summary we'd have these things to check for:
-for prefix scopes sobudget-*matchesbudget-400andbudget-5:to separate resources so right nowhydra.clientswould be replaced byhydra:clients.for specifying the permission/verbhydra:clients.readfor exampleWorkarounds or alternatives
I would have to use
.as separator exclusively, making it hard to differentiate between prefix, resource and verb in my application. Or I'd need to compile my own fosite & hydra with my custom scope strategy which adds significant complexity to my deployment pipeline & maintenance.Version
latest
Additional Context
I'd also be happy if I could just use the prefix scopes and continue to use
.as resource as well as verb separator.