General Discussion

 View Only

This Week in Support: Using aliases to resolve Single Sign On (SSO) errors

  • 1.  This Week in Support: Using aliases to resolve Single Sign On (SSO) errors

    Posted 11-03-2022 10:55
    Edited by Pat Cooney 02-06-2024 11:49

    One of the most common issues when configuring Single Sign On (SSO) is when the user's credentials (SSO Username) don't match the credentials that you have set in ProntoForms (ProntoForms Username).

    (See reference in the table below)


    In the table above you can see that the (ProntoForms Username) "jimmy" does not match with the (SSO Username) set "jredpants@thecompany.com".

    (Example adding domain suffix)

    "jimmy@thecompany.com" ≠ "jredpants@thecompany.com"


    In these situations when even adding the domain suffix the accounts will not match, we must use (SAML External Alias)

    To set an alias on the user, go to the user in the portal and follow these steps:



    In the Advance settings tab, you must add the new alias
    Remember to type the same as what you see in the "SSO Username" so that the SSO Username and SAML External Alias match.


    Once completed, the table should look like the following when the correct alias is configured on the account:

    (Example without domain suffix configured on the team)


    (Example with domain suffix configured on the team)

    Further documentation about setting up Single Sign On can be found in our product documentation portal: https://docs.prontoforms.com/1374411/Content/ProntoFormsSecurityandCompliance/Access%20Management/Configure%20SSO%20in%20ProntoForms/SetUpSSO.html


    Further documentation on user management can also be found in our product documentation portal: https://docs.prontoforms.com/1374411/Content/LandingPages/ManageUsersPermissions.htm

    #TechTalkSupport
    ------------------------------
    Julian Oller Rubio
    Support Analyst
    ProntoForms
    ------------------------------



Reminder: Content posted to our Community is public content.  Please be careful not to post Intellectual Property that you do not have permission to share.  For more information please refer to our Terms Of Use