The mapping feature allows EnterWorks to recognize attribute statement tags in the IDP's response that are different than what EnterWorks expects. To configure create the mapping file EnterWorks uses to recognize the new statement tags:
- Create a JSON file that maps the attribute statements EnterWorks is looking for to the tags
the IDP is using. The JSON file must be named:
and must be located in:sso-mappings.json
<drive>:\Enterworks\enable2020\services\sso-mappings\
- The
sso-mappings.json
file has five key:value pairs:{ "login": "login", "firstName": "firstName", "lastName": "lastName", "email": "email", "groups": "groups" }
- The key is what EnterWorks is looking for. Replace the value with the tag the
IDP is using. For example, if the IDP is using the "
email
" tag as the login value, thesso-mappings.json
file would have a key:value pair of"login": "email"
as shown below.{ "login": "email", "firstName": "firstName", "lastName": "lastName", "email": "email", "groups": "groups" }
- The
sso-mappings.json
file only needs to contain key:value pairs for the attribute statement tags that are different from what EnterWorks is searching for. For example, if the IDP is using the "email
" tag as the login value but the rest of the attribute statements are tagged as expected, thesso-mappings.json
file could only have the key:value pair for"login": "email"
as shown below.{ "login": "email" }
- Save the file.