Difference between revisions of "Single Sign-On"

Revision as of 12:16, 17 August 2018

Overview

SmartSimple provides Single Sign-On (SSO) integration through SAML 2.0. It should be noted that SSO is just a subset of federated identity management, as it relates only to authentication, and not account management or synchronization with SmartSimple.

Implementation of SSO requires configuration both within SmartSimple and within the system that will provide the authentication.

SmartSimple's implementation of SSO acts as the Service Provider and assumes the client has the infrastructure and resources to host, configure, and manage the Identity Provider service. Please contact your account manager or SmartSimple Support for further information.

SAML 2.0

SmartSimple supports SAML (Security Assertion Markup Language) 2.0 as the Service Provider through our own proprietary implementation of this standard.

Only Identity Provider-initiated authentication is supported, meaning the end user will first authenticate on the client-side system/infrastructure and then be forwarded to SmartSimple. The client Identity Provider service will construct a base64-encoded SAML assertion and send this to the user's browser. The user's browser will then relay this assertion to the SmartSimple server for SSO authentication.

Prerequisites

• You must provision your own Identity Provider service, third-party or otherwise, for use with this feature. Enabling and maintaining the Identity Provider is your responsibility.
• You must provide SmartSimple with a public key in base64-encoded X.509 Certificate format for digital signature validation.

Service Provider Configuration - SmartSimple

Within SmartSimple, SSO settings are accessed through the Global Setting -> Integration tab.

Navigating to the SSO configuration.

SSO configuration settings.

• "SSO Alias" - used to identify the SSO connection and should be configured by default to be 'SAML2'. If multiple SSO connections are to be configured then you may include an additional element on the client-side assertion named 'SSOModule' to specify the SmartSimple connection by matching a unique "SSO Alias" value.
• "Unique Identifier Field (UID)" - used to identify the user account and needs to be an attribute that is unique to each user in SmartSimple. This needs to be an attribute common to both the SmartSimple and the client-side system (typically e-mail address or employee ID).
• "X509Certificate (SAML2 Only)" - the signing certificate to be provided by the client. The formatting of this should be the certificate value without the "begin certificate" and "end certificate" header and footer lines. Also, depending on how the client-side system sends this value within the SAML assertion the certificate value will typically be formatted to just a single line but could also be multiple lines and so must be entered into SmartSimple in the same format.
• It is also recommended to disable the Session Timeout Alert setting within the Global Settings -> Security section as that feature would not be applicable to users logged in through single sign-on.
• By default, SSO acts as an additional method of authentication. If you wish to enforce the use of SSO, and restrict the regular username and password authentication, you can do so with the Global Settings -> Integration -> Enforce SSO setting which allows you to restrict a set of user roles to only be able to login through SSO.
• Bypass Two Factor Authentication - if the user has a role that has Two-Factor Authentication enabled, this setting will control whether or not the user will have to provide their Time Based One Time Password (Two-Factor) when accessing the system via SSO, or if SSO will bypass the Two-Factor requirement.
  • This feature can, for example, be used to allow users to access SmartSimple using SSO when they are within your office network, but also access SmartSimple from other locations using their username & password with the additional security provided by two-factor authentication.

Identity Provider Configuration - Client-Side System

The elements required for setup of the client-side identity provider connection are listed below.

• Unique user identifier - within the SAML assertion, this value can be sent in the standard element, or optionally within an element named 'UID'.
• Assertion Consumer Service URL - this will be equal to '/SAML2/' appended to your SmartSimple instance URL, e.g. https://alias.smartsimple.com/SAML2/.
• Service Provider's Entity ID - this can be the URL to your SmartSimple system, e.g. https://alias.smartsimple.com/.
• Service Provider metadata XML - the following is an example service provider metadata that can be used, however you must first replace every instance of 'alias.smartsimple.com' instead with the URL to your SmartSimple system.

<!--?xml version="1.0"?-->

   
      urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified
      
   
   
      SmartSimple Support
      support@smartsimple.com
   
   
      SmartSimple Support
      support@smartsimple.com
   

Active Directory Federation Services

If using ADFS refer to the below steps as related to SmartSimple for setup. Some steps unrelated to your SmartSimple configuration have been omitted.

• Add a new "Relying Party Trust".
• "Select Data Source" - Import the Service Provider metadata XML file obtained from SmartSimple.
• "Display Name" - Give the trust a display name, e.g. 'SmartSimple'.
• Finish the setup, and then return to the "Claim Rules" editor, and select the "Issuance Transform Rules" tab and add a new rule. Set the "Rule Type" to use the 'Send LDAP Attributes as Claims' template and configure the mapping to the agreed upon user identifier (e.g. LDAP attribute 'E-Mail-Addresses' to Outgoing Claim Type 'NameID'). Depending on your ADFS version and setup you may instead need to create two rules, one to map the attributes E-mail to E-mail, and then a second rule to transform the E-mail to the outgoing NameID.
• To test or use this connection use your internal ADFS URL and specify the loginToRp parameter as the SmartSimple SAML entity ID, e.g. https://adfs.yourlocaldomain.com/adfs/ls/idpinitiatedsignon.aspx?loginToRp=https://alias.smartsimple.com/.
  If you aren't automatically redirected into SmartSimple you may need to have RelayState enabled in ADFS, and then use a RelayState parameter to achieve this, e.g. https://adfs.yourlocaldomain.com/adfs/ls/idpinitiatedsignon.aspx?RelayState=RPID%3Dhttps%3A%2F%2Falias.smartsimple.com%2F%26RelayState%3Dhttps%253A%252F%252Falias.smartsimple.com%252F.

Optional Information

The following optional attributes can be used in the assertion. Please note that they are case sensitive and should be labelled exactly.

• SSOModule - used to specify the SmartSimple SSO connection when there are multiple connections configured.
• UID - can be used instead of NameID as the user identifier.
• Email
• First name
• Last name
• Department - used to update the user's organization. This will attempt to match an organization by name and will move the user to that organization if found.
• Roles - used to update the user's roles in SmartSimple. This should be a comma delimited list of SmartSimple user roles (by name) to be assigned to the user.
• Language - used to specify the initial language displayed to the user. This should be an integer value that corresponds with a language ID value in SmartSimple (e.g. 1=English).
• RedirectURL - used to specify an initial landing page in SmartSimple. This should be a relative patch (e.g. /iface/ex/ax_index.jsp).

SAML Assertion Example

The following is an example of a SAML Assertion :

<!--?xmlversion="1.0" encoding="UTF-8"?-->


   sso:saml2:alias:stage:SmartSimple:idp

   
      
         
         
         
            
               
               
            
            
            +2uvXQh+d65mNWs0G6FBf4igIxU=
         
      
      LEOCPec/eNBMqBV7A99...
   

   
      <samlp:StatusCodeValue="urn:oasis:names:tc:SAML:2.0:status:Success"/>
   

   
      sso:saml2:alias:stage:SmartSimple:idp
      
         T5014CD
         
            
         
      
      
         
           sso:saml2:alias:stage:SmartSimple:sp
         
      
      
         
           urn:oasis:names:tc:SAML:2.0:ac:classes:unspecified
         
      
      
         
            T5014CD
         
         
            david@email.com
         
         
            David
         
         
            Smith
         
         
            Shipping
         
         
            Clerk