SecureTransport as an Identity Provider

Using SecureTransport as an Identity Provider allows users to use SecureTransport as an Identity Provider. The users who authenticate using SecureTransport as an Identity Provider, will authenticate using the password stored internally in the SecureTransport, and will be treated as local accounts.

The following configuration options are added in the Server Configuration options:

  • For administrators:
    • LoginSettings.Admin.SSO.idpResolverKey
    • LoginSettings.Admin.SSO.localIdpId
  • For end-users:
    • LoginSettings.EndUser.SSO.idpResolverKey
    • LoginSettings.EndUser.SSO.localIdpId

The idpResolverKey corresponds to the Query Parameter name attribute and can be used in both a query parameter as well as a header. This is the key that will be used when requesting local or Identity Provider authentication. The default value is: idp_id.

The localIdpId corresponds to the value in the mapping that will force SecureTransport to not trigger the SSO flow and continue with local authentication. The default value is: ST_IDP.

The value of these options is configurable. For more information about how to edit the Server Configuration options, refer to Update server configuration files.

Example for using SecureTransport as a Identity Provider:

https:// <ST IP>/?idp_id=ST_IDP

Note Options for using SecureTransport as an Identity Provider can be used either as query parameters or for using requests with header.

Related Links