CentraSite 10.3 | CentraSite User’s Guide | Runtime Governance | Run-Time Policy Management | Built-In Run-Time Actions Reference (CentraSite Business UI) | Summary of Actions in the Outbound Authentication Category
 
Summary of Actions in the Outbound Authentication Category
Outbound authentication actions are used to set the client credentials to access the native API.
HTTP Basic Authentication
Used when native API enforces basic authentication. Based on the modes selected, Mediator either uses configured basic authentication credentials to invoke a native service or it uses credentials from the authorization header of the incoming request to access the native API.
NTLM Authentication
Used when native API enforces NTLM authentication. Based on the modes selected, Mediator either uses configured authentication credentials to obtain the NTLM token to invoke the native service or it uses credentials from the authorization header of the incoming request to obtain the NTLM token to access the native API.
OAuth2 Authentication
Used when native API enforces OAuth authorization. Based on the modes selected, Mediator either uses configured OAauth token to invoke the native service or it uses the OAauth token of the incoming request to access native service.
Kerberos Authentication
Used when a service provider wants a web service client that does not have the ability to generate the Kerberos token to access a service enforced with the Kerberos policy. It is also used when service provider wants a web service client to access a service enforced with the Kerberos policy.
SAML Authentication
Used when a native API enforces SAML authentication. Based on the modes selected, Mediator either uses the WSS Username mode or the Kerberos Over Transport mode to get the SAML assertion token and access the native API.