Note: below images are examples of how SAML primary keys can be set, please ensure they are set to match the current environment where SAML is being set up
Starting on version 10.2 of the K1000, SAML will allow the Primary Key (PK) to be set to something other than login. This will help avoid having users being duplicated as it will use this information to match up with users already created on the User List by using a unique identifier as the Primary Key.
Example 1:
For users in this environment, sAMAccountName is being used as the unique identifier for them (ex. sAMAccountName = pboss)
Note: if there are 2 users using pboss under Login, SAML will either match up to the first user it finds or not work at all for this user, this is why it needs to be a unique identifier found on the user
Example 2:
For users in this environment, Email is being used as the unique identifier for them (ex. UserPrincipalName = pboss@companyinc.com)
Note: if there are 2 users using pboss@companyinc.com under Email, SAML will either match up to the first user it finds or not work at all for this user, this is why it needs to be a unique identifier found on the user
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center