| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
...
Open the ZPM 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 ZPM SP Metadata file for the values in red below:
Copy the entityID value from the ZPM 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 ZPM 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 ZPM as a Service Provider (SP) in ADFS using metadata.xml file:
...
Set Name ID format to “Unspecfied”
Set Application username to “User Principal 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 UserPrincipalName to Name ID mapping and click “Finish”.
Provide Users Access to the ZPM Application
...
| 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. |
Go back into ZPM and complete the SAML SSO Configuration
...