Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
minLevel1
maxLevel7
indent10

Info

About SAML Single Sign-On in SMACSZPC

Single Sign-On can be setup in SMACS ZPC against any Identity Provider (IdP) which supports SAML 2.0.

This guide covers the steps required to setup SAML SSO against Okta, Azure AD & ADFS IdP’s.

For an exhaustive list of supported IDP’s, visit SAML-based products and services.

Install signed certificate on the SMACS machine

Note
  • Wildcard Certificates are not supported for SSO.

  1. Generate a CSR

    Image Removed
  2. Import the Signed Certificate

    Image Removed
  3. Restart Apache via the Stack8 Console (SSH)

    Image Removed

Anchor
SP-Metadata
SP-Metadata
Provide

...

ZPC Service Provider (SP) Metadata to your Identity Provider (IdP)

Once the certificate is installed and working correctly, export Export the SP Metadata to provide to your IdP.

...

If you change/renew your SSL certificate, you will need to perform the following steps:

...

Restart ZIRO Platform from the stack8-console

...

your IdP

...

.

...

Alterme identnatively, you can provide the URL to the hosted metadata.xml file to your IdP.

...

...

https://<SMACS-FQDN>:8443/saml/medatada

Adding SMACS as a Service Provider (SP) in OKTA using URL to the hosted metadata.xml file:

  1. Open the SMACS SP Metadata file you exported in the previous step to get the information required for configuring the required SAML settings in OKTA

...

  1. Copy the entityID value from the SMACS SP metadata to the Single sign on URL field in OKTA.

    In this example the value is https://stack8-demo.smacs.stack8.com:443/saml/SSO

  2. Copy the </md:NameIDFormat><md:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location= value from the SMACS SP metadata to the Audience URI (SP Entity ID) field in OKTA.

    In this example the value is https://stack8-demo.smacs.stack8.com:443/saml/metadata

...

...

Adding ZPC as a Service Provider (SP) in ADFS using metadata.xml file:

  1. Click on Add Relying Party Trust

  2. Select default option “Claims Aware”

  3. Select “Import data about the relying party from a file”

  4. Upload the Service Provider (SP) metadata file from previous step.

  5. Provide a meaningful Display Name for the SMACS ZPC relying party and click “Next”

  6. Select “Permit everyone” and click “Next””“Next”

  7. Enable “Configure claims issuance policy for this application” checkbox and click “Close”

Configure Name Identifier (NameID)

...

Configuring Name Identifier in Okta

  1. Set Name ID format to “Unspecfied”

  2. Set Application username to “AD SAM account name”

    Image Removed
  3. Click Next and then Finish.

    Image Removed

...

  1. Edit Claim Issuance Policy

  2. Click “Add Rule”

  3. Choose Claim rule template “Send LDAP Attributes as Claims” and click “Next”

  4. Provide a Claim rule name, select the Attribute Store “Active Directory” from the dropdown, provide the SAM-Account-Name value from Username Attribute from LDAP Management in ZPC to Name ID mapping and click “Finish”.

    Image Removed

Provide Users Access to the SMACS Application

In OKTA

Go to the Assignments tab of your newly created application and click the Assign dropdown to select people or groups to assign.

...

  1. Image Added

Download your Identity Provider (IdP) Metadata

Download ADFS IDP Metadata

Drop this link in your browser to download your IdP metadata.

Code Block
languagehtml
https://< hostname >/federationmetadata/2007-06/federationmetadata.xml

...

Download OKTA IDP Metadata

  1. Click on “View Setup Instructions” of the SMACS Application you created for OKTA.

    Image Removed

  2. Navigate to the bottom of the page and copy paste the contents of the box containing your IDP metadata to a text file. You will upload this file to SMACS to complete your SSO setup.

    Image Removed

...

Making changes to the OKTA applications SAML Settings (the steps completed in previous sections) will modify the IDP Metada.

...

Go back into

...

ZPC and complete the SAML SSO Configuration

  1. Import your IDP metadata

  2. Enable SSO

  3. Logout from SMACS

  4. Login to the stack8-console using s8admin account and restart the active side of the machine.

  5. Follow the instructions here on how to restart the active side of the smacs machine.

  6. ZPC

  7. Go to the SMACS ZPC URL & click the orange teal login button to authenticate using SAML SSO

  8. Use the Recovery URL to bypass Single Sign-On and to login using LDAPFor any login issues with SSO, please reach out to ZIRO Support.

Tip

SSO Configuration Complete ✔

Once logged in you will have initiated a Single Sign-On session which will give you access to all other applications registered to your IdP server without having to re log-in.