| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
| Info |
|---|
About SAML Single Sign-On in SMACS Single Sign-On can be setup in SMACS 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. |
Generate a CSR
Import the Signed Certificate
Restart Apache via the Stack8 Console (SSH)
| Anchor | ||||
|---|---|---|---|---|
|
Once the certificate is installed and working correctly, export the SP Metadata to provide to your IdP.
...
| Code Block | ||
|---|---|---|
| ||
https://<SMACS-FQDN>:8443/saml/medatada |
Adding SMACS as a Service Provider (SP) in OKTA using URL to the hosted metadata.xml file:
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
...
Fill in the Single sign on URL and Audience URI (SP Entity ID) fieldsin OKTAby searching your SMACS SP Metadata file for the values in red below:
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
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 SMACS as a Service Provider (SP) in ADFS using metadata.xml file:
Click on Add Relying Party Trust
Select default option “Claims Aware”
Select “Import data about the relying party from a file”
Upload the Service Provider (SP) metadata file from previous step.
Provide a meaningful Display Name for the SMACS relying party and click “Next”
Select “Permit everyone” and click “Next””
Enable “Configure claims issuance policy for this application” checkbox and click “Close”
Configure Name Identifier (NameID)
Configuring Name Identifier in Okta
Set Name ID format to “Unspecfied”
Set Application username to “AD SAM account name”
Click Next and then Finish.
Configuring Name Identifier in
...
ADFS
Edit Claim Issuance Policy
Click “Add Rule”
Choose Claim rule template “Send LDAP Attributes as Claims” and click “Next”
Provide a Claim rule name, select the Attribute Store “Active Directory” from the dropdown, provide the SAM-Account-Name to Name ID mapping and click “Finish”.
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.
...
In Azure AD
...
From the Enterprise Application you added in the previous steps, select Users and groups from the lefthand vertical menu.
...
...
Click on + Add user/group
...
Click on None Selected
...
...
A search panel will appear on the right hand side. Use it search for and select the individual users or groups who should be able to log into your SMACS tenant via Single Sign-Onand click Select.
...
Download your Identity Provider (IdP) Metadata
Download ADFS IDP Metadata
Drop this link in your browser to download your IdP metadata.
| Code Block | ||
|---|---|---|
| ||
https://< hostname >/federationmetadata/2007-06/federationmetadata.xml |
...
Download OKTA IDP Metadata
Click on “View Setup Instructions” of the SMACS Application you created for OKTA.
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.
| Note |
|---|
Making changes to the OKTA applications SAML Settings (the steps completed in previous sections) will modify the IDP Metada. You must re-download the latest IDP Metadata anytime a change is made to these settings. |
Download Azure AD IDP Metadata
Click on the Download link next to Federation Metadata XML
...
Go back into SMACS and complete the SAML SSO Configuration
Import your IDP metadata
Enable SSO
Logout from SMACS
Login to the stack8-console using s8admin account and restart the active side of the machine.
Follow the instructions here on how to restart the active side of the smacs machine.
Go to the SMACS URL & click the orange login button to authenticate using SAML SSO
Use the Recovery URL to bypass Single Sign-On and to login using LDAP.
...