Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

Hello everyone! We have got a question regarding Hydra and OpenID Dynamic Client Registration. We secured the endpoint with  Oathkeeper  validating the software statement. What we cannot understand is how to limit what scopes are available/allowed to requests. Would you recommend any approaches to do this. We want the public clients (the mobile App) to only request 'read' scopes for the tokens. Thank you!

We see that some of the Open Bank APIs use approach when selected scopes are asserted using software_statement's scope claim. We are going to try to do this using OathKeeper. Do you think this is a nice approach?