Versions Compared

Key

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

Table of Contents
minLevel1
maxLevel7
indent10

...

  1. Fill in the Single sign on URL and Audience URI (SP Entity ID) fieldsin OKTAby searching your ZPC SP Metadata file for the values in red below:

    1. Copy the entityID value from the ZPC 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 ZPC 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. Set Name ID format to “Unspecfied”

  2. Set Application username to “User Principal name”“sAMAccountName”

  3. Click Next and then Finish.

Configuring Name Identifier in ADFS

...

Note

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

You must re-download the latest IDP Metadata anytime a change is made to these settings.

Go back into ZPC and complete the SAML SSO Configuration

...