Forum Discussion

Dani's avatar
Dani
Advisor
9 years ago
Solved

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.

16 Replies

  • ChristineC's avatar
    ChristineC
    Khoros Alumni (Retired)
    9 years ago

    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.

  • Dani's avatar
    Dani
    Advisor
    9 years ago

    Thanks Christine!

    Much appreciated.

     

    Regards,

    Dani

  • Dani's avatar
    Dani
    Advisor
    9 years ago

    We had interstitial page removed on stage and now running in to the below issues:

     

    We were expecting after removal of interstitial page that the registration would be completed and user id generated and displayed.

    We are seeing the following on stage:

    1) User ID is not being generated and or displayed as far as we can tell
    2) No confirmation message is being displayed "thank you for completing your profile your user name is ...."
    3) My user-id https://dojo.stage.domo.com/t5/user/viewprofilepage/user-id/475 but again no user name has been successfully generated

    4) This account is incomplete as it has no ability to post reply or engage.

    5) as an aside removal of the interstitial page has disabled ability for anyone to change user names including admins.

    I have support engaged but welcome your insights here!


    We want this process to be seamless as soon as the token is generated, auto create a user name and display confirmation message without additional intervention from user

    Thanks!
    Dani

  • ChristineC's avatar
    ChristineC
    Khoros Alumni (Retired)
    9 years ago

    Sorry if it was not clear.  I'll try again. Prior to disabling the SSO Registration page you will want to do a user export to identify users that are missing any required fields.  Those fields must be populated either in a batch update or upon their next authentication for community. Then going forward, your IDP will need to manage those fields (in other words auto generate the login names and send over any other required fields in the SSO token).  

     

    The pre-population of login name feature and success message are tied to the SSO Registration page so if the page is disabled that logic must be handled by your IDP.  Either the required fields can be managed by the SSO Registration page or your IDP.  Anything in between sounds like a customization and I'd recommend engaging Professional Services.

     

     

     

     

     

  • Dani's avatar
    Dani
    Advisor
    9 years ago

    Thanks for the updated information!

     

    1) Do I engage Lithium to help manage a batch upload? The only field missing is "username". Every registered user whether partial or complete has a Lithium ID. I am able to extract a list of al partial registrations in an excel or CSV file, I simply need to understand the process to do a batch upload and randomly assign user names. 

     

    2) Do all of the legacy partial registrations need to be 100% complete before we go on to the next steps?

     

    3) Can you clarify what IDP stands for again?

     

    4) It sounds like we will need to generate usernames on our end of the SSO token generation which would then be passed to Lithium going forward, otherwise we are looking at a customized solution, correct?

     

    Thanks!
    Dani

  • Dani's avatar
    Dani
    Advisor
    9 years ago

    5) Lastly if we do not update all legacy partial accounts will we still be able to address the new ones created or is there some sort dependency on cleaning up the legacy accounts?

     

    Thanks!
    Dani