[Index]

Model: relation/HcsSsoSpREL

SSO SP Settings

Full HTML Help

Configure SSO for VOSS Automate

This procedure configures self-service Single Sign-On (SSO) for VOSS Automate.

Prerequisites:

• Create a self-signed or third-party-signed system certificate. See SSO Certificate Management.

• The VOSS Automate server and the IdP server must be configured so that their clocks are synchronized.

  You can define the number of seconds of permitted clock drift between VOSS Automate and the IdP. The number of seconds for tolerance is customizable, and this value must be set in accordance with the deployment's security policy. By default, VOSS Automate uses a value of 0 for clock drift; that is, assume clocks are exactly in sync.

• You must be a high-level administrators logging in above the Provider admin level to perform this procedure.

To configure self-service Single Sign-On (SSO) for VOSS Automate:

1. Log in to VOSS Automate as hcsadmin.

2. Go to (default menus) Single Sign On > SSO SP Settings.

3. Click Add.

   Note

   Configure only one instance of SSO SP Settings.

4. On the Base tab (or pane):

   • (Mandatory). From the System Certificate drop-down, choose the signed third-party system certificate to use.

     Note

     Choosing an unsigned third-party-signed certificate will result in an error. For details around renewing an expired certificate, see Renew Single Sign-On Certificate for Automate.

   • At Validity (Hours), to allow the SSO SP setting to expire, enter a number of hours. This is the validity period (in hours) that the metadata is valid for.

5. On the SAML SP Settings tab (or panel):

   • (Mandatory). At FQDN of the Server, fill out the server FQDN.

     Note

     The FQDN that will be embedded in the SP metadata for this IdP for URLs that refer back to the Service Provider. The FQDN of the server is stored in the SP metadata that is uploaded to the IdP. The SSO login URL then contains the fully qualified domain name (FQDN):

     https://<FQDN of the Server>/sso/<login_URI>/login

     If you have configured a custom hostname for SSO user login, enter it here. Upon login, the IdP will redirect you to this FQDN.

   • Select the relevant checkboxes, based on your security environment and requirements:

     • Sign Authn Requests

       Defines whether outgoing authentication messages will be signed. If yes, the specified private key will be used. By default, this is False (unchecked). If one of your identity providers has WantAuthnRequestsSigned set in its metadata, then select this checkbox (set to True).

     • Want Assertions Signed

       Defines whether assertions should be signed. Only select Want Reponse Signed if you’re sure that all IdPs sign responses.

   Note

   If a secure connection is required with the secure attribute set on the cookies, the URL values for bindings of end points must be specified with https.

   The Assertion Consumer Service fields define how SAML requests and responses map on to standard messaging and communications protocols.

6. Save your changes.

   Note

   Saved SSO settings are published by the VOSS Automate service provider and are available from metadata URL, for example: http://mydomain/sso/metadata. SSO service provider configuration requests to this URL automatically trigger an xml file download of the specified SSO service provider configuration.

7. View the location of the VOSS Automate SP metadata that you will upload to the IdP:

   • Go to (default menus) Single Sign On > SSO SP Metadata.
   • Point your browser to the URL shown here.
   • Save a copy of the SP metadata.

8. Upload SP metadata to the IdP:

   Refer to your IdP documentation for details on configuring SSO on your IdP..

   The IdP must release the UID and map it to an appropriate attribute. For example, an IdP that authenticates with Active Directory can map the UID SAML attribute to sAMAccountName in the Active Directory server.

9. Download IdP metadata from the IdP server.

   Refer to your IdP documentation for details on downloading IdP metadata.

   If an expired SSO certificate is being renewed and the IdP metadata has not changed, then the download, configure, and upload of the IdP metadata is not required.