By default, SPS assumes that the Starling username of the user is the same as the gateway username (that is, the username the user used to authenticate on SPS during the gateway authentication). To identify the users, SPS uses the username (login) field in Starling, which is an email address.
If the gateway usernames are different from the Starling usernames, you must configure the SPS Starling plugin to map the gateway usernames to the Starling usernames. You can use the following methods:
To simply append a string to the gateway username, configure the append_domain parameter. In this case, SPS automatically appends the @ character and the value of this option to the username from the session, and uses the resulting username on the Starling server to authenticate the user. For example, if the domain is set as append_domain: example.com and the username is Example.User, the SPS plugin will look for the user Example.User@example.com on the Starling server.
To look up the Starling username of the user from an LDAP/Active Directory database, configure the [ldap] section of the SPS Starling plugin. Typically, the SPS plugin queries the email address corresponding to the username from your LDAP or Active Directory database. For details on LDAP parameters, see [ldap].
If you configure both the append_domain parameter and the [ldap] section of the SPS Starling plugin, SPS appends the @ character and the value of the append_domain parameter to the value retrieved from the LDAP database.
If you have configured neither the Domain parameter nor the [ldap] section, SPS assumes that the Starling username of the user is the same as the gateway username.
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center
