Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
User attribute mapping is used for identifying fields in the Service Provider that you want to map with those in the IdP server by synchronizing them on login. It compares the values in the SAML response in case-insensitive manner by default.
You can map any user field to any arbitrary SAML attribute. For example, you can map the user’s username as a Name.
Mapping SAML assertion attributes to Adeptia user fields can be performed by setting the values for the following environment variables in the portal section of the global values.yaml file.
| Variable Name | Default value | Description |
|---|---|---|
| SAML_SSO_MAPPINGS_0_NAME | The Adeptia user field | |
| SAML_SSO_MAPPINGS_0_MAPPEDATTRIBUTE | subject.nameid | The SAML assertion attribute |
| SAML_SSO_MAPPINGS_0_IGNORECASE | true | The environment variable to set the fields' value comparison to be case-sensitive. Setting its value to false makes the fields' value comparison case-sensitive. |
If you want to create another mapping, you need to use the number in incremental fashion. You will be using number 1 (one) in the variable name for the next mapping, for example, SAML_SSO_MAPPINGS_1_NAME.
Once you've mapped the fields successfully, the next step is to create users in Adeptia Connect.
| Info |
|---|
| The user must exist both in SAML and Adeptia Connect. For information on how to create users, refer to Creating users. |
| Panel | ||||
|---|---|---|---|---|
| ||||
What is new |