SSO email case sensitivity
šAuthenticationš¬Self-hostedšŖµLogināQuestion
Use-case: We use Zitadel as authentication for our company product.
Environment: Self Hosting
Version: 4.4.0
Stack: Typescript app (React Router), Postgres
What you expected to happen: I connected our company Microsoft Entra to our dev instance of Zitadel. I would like to login to our app using SSO.
What went wrong: Each customer has their own instance of our app, a Postgres database and their own instance of Zitadel. The customer can create new users in our app, which then creates the users in Zitadel and saves the Zitadel user id in the Postgres database. When I set up SSO, it throws an error if the user's email cases do not match what is in Zitadel. For example: Zitadel has "user@example.com" saved and Entra has "User@Example.com". This prevents the user from logging in with their correct email address. The issue is that we lowercase all emails (in our app) before creating the Zitadel user for consistency. We could undo this, but then customers would need to make sure they are inputting new users in the app with the exact same case sensitivity as the their IDP, which they may not have access to. Is there a way to normalize cases in user lookup via SSO? If not, is there a plan to implement this? We need to keep our app as the source of truth for users and prefer not to force customers to be that nitpicky when entering new users.
Environment: Self Hosting
Version: 4.4.0
Stack: Typescript app (React Router), Postgres
What you expected to happen: I connected our company Microsoft Entra to our dev instance of Zitadel. I would like to login to our app using SSO.
What went wrong: Each customer has their own instance of our app, a Postgres database and their own instance of Zitadel. The customer can create new users in our app, which then creates the users in Zitadel and saves the Zitadel user id in the Postgres database. When I set up SSO, it throws an error if the user's email cases do not match what is in Zitadel. For example: Zitadel has "user@example.com" saved and Entra has "User@Example.com". This prevents the user from logging in with their correct email address. The issue is that we lowercase all emails (in our app) before creating the Zitadel user for consistency. We could undo this, but then customers would need to make sure they are inputting new users in the app with the exact same case sensitivity as the their IDP, which they may not have access to. Is there a way to normalize cases in user lookup via SSO? If not, is there a plan to implement this? We need to keep our app as the source of truth for users and prefer not to force customers to be that nitpicky when entering new users.
