Forum Discussion

Dani's avatar
Dani
Advisor
9 years ago

Auto generate SSO User Login guidelines, how can you manage parameters of user id?

Greetings,

 

We currently have a fully integrated SSO which passes our product login credentials to Lithium. We then have an opt in where customers must click on a link "complete registration" to reach the complete registration page in order to create a user ID and accept terms of use.


We are looking to auto create user id in to improve our completed registration rates.

 

In our current SSO set up:

 

  1. customers login into Domo product
  2. Select Community from our dice graphic icon
  3. They are then brought to community and must click on one of 3 options to “Complete Registration”
  4. They then arrive a the Complete Registration page where  they select a user name, accept terms and click on submit
  5. See this link here

 

Question I have is.

 

If we enable “Auto generate SSO User Login”

 

I assume the system will auto generate a user name, correct?

 

 

Is there a way where we auto populate and completely by pass the registration page which is auto completed and terms accepted by default? How can we manage what the auto assign user id will look like? In other words if we pass a customers email can we write a script to state take 1st 3 letters and last 3 letters or email before their domain?

 

Can you send me any relevant documentation on this?

 

Thanks!
Dani

 

  • Hi Dani, right next to the "Auto generate SSO User signin" setting there is also an "XML Text Generator for SSO User signin" which must also be filled out.  Here's an example of prepopulating the login with first and last name.  Here's a another example that will generate logins like "user06576". Some customers prefer this approach rather than using partials of email or first and last name for privacy reasons.

     

    <textGenerator>
        <text key="sso.user_login.auto_generate.prefix"/>
        <number min="1" max="10000" prefixZeros="true"/>
    </textGenerator>

    If you have other fields currently configured to be collected on the interstitial page, then you likely won't want to bypass the page entirely.  For example, terms of use specific for community

  • That is correct. If the SSO registration page is disabled and the fields currently configured for that page will be managed by your IDP, then a newly created user will arrive on the community without any extra registration steps.

     

    I don't know of another OOB (out of the box) welcome/success message for newly created SSO users. Perhaps you can create a custom one.

  • ChristineC's avatar
    ChristineC
    Khoros Alumni (Retired)

    Hi Dani, right next to the "Auto generate SSO User signin" setting there is also an "XML Text Generator for SSO User signin" which must also be filled out.  Here's an example of prepopulating the login with first and last name.  Here's a another example that will generate logins like "user06576". Some customers prefer this approach rather than using partials of email or first and last name for privacy reasons.

     

    <textGenerator>
        <text key="sso.user_login.auto_generate.prefix"/>
        <number min="1" max="10000" prefixZeros="true"/>
    </textGenerator>

    If you have other fields currently configured to be collected on the interstitial page, then you likely won't want to bypass the page entirely.  For example, terms of use specific for community

    • Dani's avatar
      Dani
      Advisor

      ChristineC

       

      Thanks for the quick reply this is very helpful!

       

      As of today the registration page requires creation of a user id and accepting terms of use.

       

      Since they have already done so in signing in to our product we may be able to bypass this. I am reviewing this aspect with legal next week.

       

      I needed to understand the logistics here and options to auto generate a user id.

       

      Much appreciated!
      Dani

       

      • Dani's avatar
        Dani
        Advisor

        One more item, it doesn't sound like we would need to make any changes to existing SSO code aside from modifying the internal Lithium Admin settings:

         

        • Auto generate SSO User signin
        • XML Text Generator for SSO User signin

        Thanks!

        Dani