Implementing RBAC using okta

user_1912454 0
Viewed 766

Currently our spring boot app uses okta for login. There is a need to implement RBAC for the application so I was trying to see if I can leverage okta itself for mapping users to specific roles.

I would like to implement the standard RBAC model in which I would map multiple permissions under a role and the roles are associated to users. Basically it involves 3 levels permissions > roles > users.

But in okta I don't see the standard way for mapping roles and permissions. RBAC is achieved by creating groups and associating groups to the users, which is two levels. And groups needs to be added as a custom claim.

How do I achieve the standard RBAC mapping(permissions > roles > users) in okta or it's something that needs to handled outside the IDP provider.

Thanks in advance.

idp okta spring-boot openid-connect rbac
2 Answers

Possible Solution:

You can make the scopes (scp in access token) be your permissions. Below are the steps:

  1. In your Authorization Server, create your custom scopes(permissions) and set them as default scopes (this is necessary). For example create 2 default scopes:
books.read (default=true)
books.write (default=true)

  1. Go to access policies in your Authorization Server create one if none is defined.

  2. Create access policy rules in the access policies page, the rules will be your mapping between groups and scopes.

  3. Test that in Token Preview tab, the trick here is to leave scopes field empty so that the Authorization server can return the default scopes that are set for the user, as explained by Okta:

A default scope will be returned in an access token when the client omits the scope parameter in a token request, provided this scope is allowed as part of the access policy rule.

  1. Now in your application when requesting an authorization code make sure that scope query param is empty.

  2. Depending on the library you are using you may face some issues if by default they are expecting an id_token to be always returned but you will probably be able to customize it. For example: https://github.com/okta/okta-auth-js/issues/827

Solution Limitations:

As mentioned in steps 4 and 5 we are omitting the scope query parameter, this mean that only our custom scopes assigned for the user or his groups will be returned, since the base scopes that are predefined by Okta such as profile, openid, email ... will not be returned. Which also means that we are skipping OIDC which needs the openid scope, so id_token will not be returned and only an access_token will. So this solution assumes that you don't need any of the base scopes predefined by Okta.

In case you need any of the base scopes

As described in the limitations, the solution assumes that you don't need any of the base scopes predefined by Okta. But in case you do then below is a solution that works in that case but not that nice.

When requesting an authorization code in the oauth flow, you need to send the request twice

first one: omit scope query param, so the default scopes are returned.

second one: append the returned scopes returned from the first request to the list of base scopes you wanted such as openid, profile, 'email`. So you would send something like (encoded already)

?scope=books.read%20books.write%20openid%20profile%20email

Disclaimer:
The above solution may not be recommended, but it works. If anyone can find any security issues with the above solution please leave it in the comments.

user_50891530

When you get into the details of roles and permissions, the data tends to be domain specific and to change often. I would advise against trying to manage it in the Authorization Server.

One design pattern that will give you full control over claims is to form a custom AuthenticationPrincipal that includes roles or permissions from your application database(s).

If interested in this pattern, see these resources of mine:

user_90198850
Related