Skip to main content

Hi - A quick question around how the Insided platform would handle below scenario specifically around user accounts:

Context: We need to create 2 SSO login options/buttons (SAML2 for our customers and Open ID for our employees) on the login page of our private community and the associated backend SSO integrations. We will NOT pass username in the SSO profile data (only id, email and custom roles)  as we want our users to create a username when they login first time.

Scenario: Employee1 (with email employee1@test.com) logs in via Open ID sets a username, etc and interact with community. And then during their second or future visit they login using SAML2.

 

Questions: Given that the email is still the same employee1@test.com 

  1. what will the user experience be when they login using SAML2 (will they be allowed to login or will it reject due to duplicate email)
  2. If the user (Employee1) is allowed to login via SAML2 will the insided platfrom create 2 separate accounts with same username or will the platfrom consolidate both different SSO login methods into one Insded account?

Hi @ruc 👋,

  1. They will be able to login if the email address is the same and a separate account with the same SSO ID doesn’t exist.
  2. It will be one account as different accounts with the same username cannot exist.

Let me know if you have any further questions!

Reply


Terms & ConditionsCookie settings