Repository navigation
[FEATURE] Support OAuth User Attribute Mapping #1025
Description
Activity
Added with #1087.
You will be able to use the following mappings:
# Username claim. TINYAUTH_OAUTH_PROVIDERS_name_CLAIMS_USERNAME= # Email claim. TINYAUTH_OAUTH_PROVIDERS_name_CLAIMS_EMAIL= # Name claim. TINYAUTH_OAUTH_PROVIDERS_name_CLAIMS_NAME= # Groups claim. TINYAUTH_OAUTH_PROVIDERS_name_CLAIMS_GROUPS=
However, I am not sure if I should allow
subas well because it's technically a requirement and an OpenID Connect server MUST include it in the response.Reacted by DanielNI do not think the
subclaim should be a problem.
Nextcloudsocs.data.idis static and cannot be changed without recreating the entire user.
So I would just setusernameandsubto the same value.
I cannot say anything for other applications.Whatever is easiest for you. I am happy as long as I no longer get errors.
I know that this is not an officially supported OIDC Endpoint. This uses OAuth2. I do not know much of the official standard.
But I also set up Pocket ID so that is my alternative if something does not work.
Is your feature request related to a problem? Please describe.
I want to connect tinyauth to nextcloud but it seems that the user endpoint does not return all the data (email in this case) in the expected structure.
Describe the solution you'd like.
It would be nice to have some simple json mapping where one can just remap the location of the provided userinfo.
Example:
Additional context
There already is a similar Issue with Grafana: https://help.nextcloud.com/t/oauth2-userinfo-api/70556/12
An example structure for nextcloud user can be found here: https://docs.nextcloud.com/server/latest/developer_manual/client_apis/OCS/ocs-api-overview.html#user-metadata
Human Written Confirmation