You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload
8000
to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 11, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 11, 2026. It is now read-only.
OIDC Plugin : Using CUID as Username Instead of Email. #95
Hi,
I'm using your OIDC plugin, but the version I'm currently using (4.14.2) uses the user's email address as the username. However, I want to use the CUID (Customer User ID) sent by the OIDC server instead because I'm considering replacing my SAML-based authentication system with OIDC. To ensure a smooth transition and maintain the integrity of user data, I would like OIDC to have the same user identification behavior as SAML, which means using the CUID as the username, to prevent the creation of duplicate users when implementing OIDC. Is this possible with the OIDC plugin?
Thank you in advance.
Reacted by tschoesi, Jens Rauch, L. Bensaadi, vladimirdulov and OrangeTech-Melissa
The attached patch should get you most of the way there - you will need to change $result->nickname to correspond with the OpenID Claim your provider returns.
Activity
bcooksley commentedon Dec 21, 2023
The attached patch should get you most of the way there - you will need to change
$result->nicknameto correspond with the OpenID Claim your provider returns.kde-changes.txt
The plugin uses email instead of username to create users
vladimirdulov commentedon Nov 13, 2024
A PR submitted to sort this issue.
OrangeTech-Melissa commentedon Dec 3, 2024
Thank you for the update!