FAQs about Auto Provisioning

Updated 

Clear your doubts and avoid confusion with the answers of some FAQs about user auto provisioning in this article. If you want to understand what User Auto provisioning is, you can refer to this article for more details.

FAQs

  1. What is an SSO attribute?
    An SSO attribute is a characteristic or trait of an entity that describes the entity. It is a ‘name:value pair.’ The attributes included in the SAML assertion correspond to certain attributes of the service provider to convey user information from the identity provider to the service provider (Sprinklr).

  2. How do I add SSO attributes to my IDP Settings?

    The client should reach out to their IT team so that they can make necessary changes in the IDP settings to add the attributes required while sending SAML responses. Every IDP has their respected way of adding new attributes which is usually familiar to the IT team for every client. You can refer to the following link for a detailed explanation of the same:

    https://documentation.commvault.com/2022e/essential/97758_mapping_saml_attributes.html

  3. Can I create users as part of different groups using Auto provisioning?

    By using auto provisioning we can create different user groups based on the SSO attributes received. There are two ways in which we can do this:

    • Based on the SSO attributes we will directly map the data to specific Sprinklr fields for differentiating between different user groups. Example of some fields: Country, Role/Persona, Department, User Type, etc.

    • We can also allot custom field values for users to add them to a group by configuring user rules based on another field value received by SSO attribute. Here is an example for this:

      • If SSO attribute Country = “Spain” should drive two custom fields in Sprinklr for Country and Group, then :

        • Map SSO_Country in the mapping sheet to a Custom Field_Country

        • Enable a User Rule in the Rule Engine:

          • Set the condition: Custom Field_Group = “EMEA” 

          • Set the action: Custom Field_Country = “Spain”