I’m trying to setup owncloud with single sign on using Authentik. I have it working for normal users. There is a feature that allows automatic role assignment to users so that admin users from authentik become admin users for owncloud.
This is described here: https://doc.owncloud.com/ocis/next/deployment/services/s-list/proxy.html#automatic-role-assignments.
In this document, they describe having attributes like
- role_name: admin
claim_value: ocisAdmin
The problem I have is I don’t know how to input this information into an Authentik user. As a result, owncloud is giving me this error:
ERR Error mapping role names to role ids error="no roles in user claims" line=github.com/owncloud/ocis/v2/services/proxy/pkg/userroles/oidcroles.go:84 request-id=5a6d0e69-ad1b-4479-b2d9-30d4b4afb8f2 service=proxy userid=05b283cd-606c-424f-ae67-5d0016f2152c
Any authentik experts out there?
I tried putting this under the attributes section of the user profile in authentik:
role_name: admin
claim_value: ocisAdmin
It doesn’t work and it won’t let me format YAML like the documentation where the claim_value is a child of the role_name.
You can do this by replacing an existing scope or creating a new one. In some cases I’ve needed to replace an existing scope with custom mappings, and add the information needed to it. For example I created a custom scope of ‘profile’, added the relevant claim needed along with the standard scope information, and then associated that to the provider.
To do that, you add an OAuth scope mapping,. That mapping will then add the desired claim information. These are created with small python scripts. Set them to add the relevant claim when a case is matched (ex. User is in group “Admins”). Name the scope “profile”, though it could be a new scope (preferred) if owncloud lets you specify them.
In the provider for owncloud add that new or replacement scope. In the Edit settings that’s found under Advanced Protocol Settings. You’d add the named scope that correlates to your recently created Claim.
Then verify everything is working as expected; Go to Preview for that Provider. While it won’t show you scope names, it will combine the claims into the JWT preview which is convenient for validating you did everything correctly. It helps reduce the extra variable of Owncloud until you get to that point.
Roles in authentik are for permissions in authentik. You want a group instead. Group memberships are send via OIDC.
tried this, created a group called ocisAdmin and added the admin user to it, it still gives the same error. Seems like I need to define a proxy.yaml file in owncloud with the roles, I did this and it still doesn’t work.
In the oidc provider in authentik you have to enable sending the groups. I forgot what its called.
not an authentik user, but after skimming their docs i think you have to:
- create a role “ocisAdmin” via authentiks admin interface
- give this role to a group in the admin interface or create one.
- assign a user thats supposed to be an owncloud admin to the group
it might be that you also have to define somekind of mapper to include this in the informations owncloud receives from authentik, but as i said i only skimmed the docs and would personally just try it without the mapper.
tried this and also tried making a role in authentik assigned to the group called ocisAdmin and added the admin user to it, it still gives the same error. Seems like I need to define a proxy.yaml file in owncloud with the roles, I did this and it still doesn’t work.
does authentik offer an option to preview a jwt for a given user? might be as simple as that the claim is not named “ocisAdmin” or is not a toplevel entry in the jwt.
Reminds me of the group limit attribute in nextcloud. You could try looking at the ‘Custom profile scope’ section of https://docs.goauthentik.io/integrations/services/nextcloud/ to see if it helps to work out what to do
this is great info, thanks. I don’t think its the issue right now, I think I need to define the roles in owncloud which I tried to do but it still doesn’t work. I’ll ask on the owncloud forums but these custom scopes might still be needed at some point. thanks.
