You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the OIDC "subject" field (sub), kanidm uses a UUID for this field and uses the preferred_username for a fully qualified username (e.g. [email protected]).
I would like to use this field instead, since not all users need to have an email address defined in their profile.
I have tried using subject, full-email and local-part options for the oidc.user_id_method
I would also like to be able to use the scopes field to map to the @groupname.
The text was updated successfully, but these errors were encountered:
Hm at the moment only email and subject are supported to derive the username from. Groups are not supported for OIDC at the moment.
Lets leave this here as a reminder to support more freely configuration for OIDC when the planned rewrite (sadly already planned for quite a time) happens.
I'm using kanidm as my OIDC provider.
In the OIDC "subject" field (
sub
), kanidm uses a UUID for this field and uses thepreferred_username
for a fully qualified username (e.g.[email protected]
).I would like to use this field instead, since not all users need to have an email address defined in their profile.
I have tried using
subject
,full-email
andlocal-part
options for theoidc.user_id_method
I would also like to be able to use the
scopes
field to map to the@groupname
.The text was updated successfully, but these errors were encountered: