Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

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 NameDefault valueDescription
SAML_SSO_MAPPINGS_0_NAMEemailThe Adeptia user field
SAML_SSO_MAPPINGS_0_MAPPEDATTRIBUTEsubject.nameidThe SAML assertion attribute
SAML_SSO_MAPPINGS_0_IGNORECASEtrueThe 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.

The user must exist both in SAML and Adeptia Connect. For information on how to create users, refer to Creating users.
  • No labels