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 r...
  • ChristineC's avatar
    ChristineC
    9 years ago

    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

  • ChristineC's avatar
    ChristineC
    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.

ChristineC's avatar
ChristineC
Khoros Alumni (Retired)

I'm not aware of many cases where the SSO registration page is turned off after it has been enabled.  Typically it is turned on because there are pieces of data not available with the customer's IDP such as login (they don't have a username that is appropriate for forums), missing emails, or as mentioned previously community specific terms of use.  

 

Note that once you disable the SSO registration page, any fields that were previously managed by the community will then need to be handled by your IDP.  In that case, it may not make sense to have a 'registration success' page in the community as it should be a seamless experience at that point.  I am not aware of a feature for batch updating partially registered users with random, uniquely generated usernames.  One option may be to use the user export admin tool to help with that process or you can engage Professional Services.  

 

Another option is delaying display of the SSO registration page until a user performs an action that requires a username (such as message posting), but I think you may already be using this in your community

 

 

 

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