How does one map Okta terminology to SecureAuth for SAML integrations

Follow
    Applies to:
  • SecureAuth Identity Platform
  • Legacy SecureAuth IdP
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected:  All

    Description:  

    Okta and SecureAuth use slightly different terminology when creating a SAML application. This KB will show what those mappings are equivalent to.

     

    Cause:  

    Different terminology between documentation may cause some confusion over configuration settings.

     

    Resolution:  

    OKTA SAML Terminology SecureAuth SAML Terminology
    Single sign on URL SP Start URL
    Recipient URL SAML Recipient
    Destination URL SAML Consumer URL
    Audience URL SAML Audience
    Default RelayState WSFedReply To/SAML Target URI

     

     

    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful

    Comments

    0 comments

    Please sign in to leave a comment.