SSO allows admins to easily login to SafeConsole using 3rd party authentication. ONELOGIN, PINGONE, and PINGFEDERATE support is currently in beta. With Single Sign on enabled SafeConsole Admins can be synced from a centrally managed repository of users that allows for easier review and management. 


----------------------------


Below are KB articles for each supported SSO solution:


PingOne: http://support.datalocker.com/support/solutions/articles/4000127687-pingone-sso-integration-with-safeconsole-5-3-


OneLogin: http://support.datalocker.com/support/solutions/articles/4000127686-onelogin-sso-integration-with-safeconsole


PingFederate: http://support.datalocker.com/support/solutions/articles/4000123302-pingfederate-integration-with-safeconsole


Integrating your SSO solution into SafeConsole



Login to your SafeConsole server - Server Settings > Single Sign On


Select the SSO solution you wish to integrate


Upload your SAML Metadata file. All of the fields should populate with the appropriate information. 


Once the information is saved, logout and you will now have the ability to log into the console using your SSO Solution. 





 Adapter connection settings: (More details of these settings can be found within the KB of the solution you wish to use)


Adapters are used to authenticate users to SafeConsole. You must create an instance of the adapter the SP connections may use to fulfill attribute contracts sent to SafeConsole.


Extended Contract:

Attribute:
policy.action
Attribute:
username
Attribute:
givenName
Attribute:
mail
Attribute:
memeberOf
Attribute:
objectGUID
Attribute:
sn
Attribute:
userPrincipalName


Adapter Contract Fulfillment:

mail:
mail (Adapter)
policy.action:
policy.action(Adapter)
givenName:
givenName (Adapter)
objectGUID:
objectGUID(Adapter)
memberOf:
MemberOf (Adapter)
sn:
sn(Adapter)
userPrincipalName:
userPrincipalName(Adapter)
username:
username (Adapter)