Source

SSO, directory sync & provisioning — found from sitemap — Secret Server

Checked for Secret Server on 20 Oct 2026

Technical details

type: page
http status: 200
content hash: sha256:d34ead6c6e555ac902e0413662fa9d19298e714d7873f71319f9da7cd23988f5
permission: robots_ok
screenshot: Screenshot on file (internal exhibit, not published)

Cited by

SAML okta integration Report an error

“Setting Up OKTA for SAML (Secret Server)”
SAML slo support Report an error

“check the Allow Application to Initiate Single Logout check box for Enable Single Logout option.”
SAML metadata import Report an error

“Click Import IDP from XML Metadata and select the Okta metadata.xml file you saved previously.”
SAML configuration location Report an error

“navigate to the SAML configuration page (Admin > Configuration > SAML tab) and click Create New Identity Provider”
SAML assertion consumer URL Report an error

“https://[YourSecretServerInstanceName]/saml/assertionconsumerservice.aspx”
SAML slo URL Report an error

“Single Logout URL is your [SecretServerInstanceName] followed by the URL string: /saml/sloservice.aspx”
SAML metadata URL Report an error

“SP Issuer is the link to your Secret Server's SAML Metadata, which is just the [InstanceName]/samlemetadata”
SAML certificate upload Report an error

“Signature Certificate is the public key (.cer) file that corresponds to the .pfx you uploaded into your Secret Server Service Provider”
SAML browser requirement Report an error

“Due to browser issues, use the FIREFOX or IE browsers to complete this section (do NOT use Chrome)”
User provisioning okta Report an error

“Click Assign Applications, then click Assign next to your Secret Server Service Provider Enter the User Name of the corresponding user from Secret Server”

1 fact read from this page is not shown because it could not be confirmed on the page as captured.