[OpenID] Beginner's Question: Per-Function-Access-Rights

[Quipsy] Markus Karg karg at quipsy.de
Mon May 16 14:29:50 UTC 2022


I am new to OpenID and OAuth2 and read several tutorials and references but there is one problem left open I hope you can help with.

Our existing application does RBAC with the addition of a complex system of functionality-grained access rights. This means, an authentication token must contain not only roles a user has, but also additional functionalities he is allowed to do. Example: A user that is in the role „Editor“ might have (or might not have) the additional right to execute a special function X. As our application is huge, besides lots of roles there are literally hundred of optional functionalities he could be granted or not. To our knowledge, this is not covered by any of the existing authentication services / products.

We did not find a solution for this in „pure“ OpenID Connect / OAuth2, so currently we discuss the following attempts:


  1.  Let OpenID Connect do ONLY Authentication but not Authorization. This means, our client sends the obtained ID Token to our existing custom authorization service in exchange for a custom authorization token containing the roles AND the per-function-grants.



  1.  Let OpenID Connect do BOTH Authentication and Authorization, but wrap each single function-based-grant as a role. In the end, this means a token needs to contain literally hundred of roles in turn, which makes it unmanageable in literally all OpenID Connect services / products we evaluaged so far.


  1.  Maybe there is a standardized flow that allows an authorization service dynamically lookup the function-based-grant from our custom authorization service?

Maybe there are other solutions to that problem, but we could not image them.

Any comments welcome (besides: do not use per-function-access-rights as this is axiomatic for our product)! 😊

-Markus


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20220516/acef35e5/attachment.html>


More information about the general mailing list