SOA Governance and API Management : Administering Mediator : The Built-In Run-Time Actions : The Built-In Run-Time Actions for Virtualized APIs : Outbound Authentication Actions
Outbound Authentication Actions
Mediator provides the following categories of outbound authentication actions:
Outbound Authentication Actions
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 API.
*Kerberos Authentication: Used when service provider wants a web service client that does not have access to the KDC server, 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 using non LDAP user credentials.
Copyright © 2015- 2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback