Authenticate Enterprise Gateway client user credentials specified in an HTML form.
Authenticate a client of the Enterprise Gateway using HTTP basic authentication.
Use HTTP digest authentication to authenticate a client.
Allow or deny access to protected Web Services based on the IP address of the client machine.
Authenticate clients by their SSL certificates.
Consume a Kerberos token to authenticate a Kerberos Client.
Obtain a service ticket for a Kerberos Service and use it to authenticate to the service.
The Enterprise Gateway can authenticate a client based on the value of a Distinguished Name, X.509 Certificate, or user name in an HTTP header.
Use this filter to authenticate a user based on a username and a password that have been stored in Oracle message attributes.
Validate the information contained within a SAML authentication assertion.
Validate the XML Signature over a SAML authentication assertion.
Request an authentication decision from a SAML PDP based on an authenticated user's credentials.
Validate the XML Signature over a SAMLP response.
Validate the XML Signature contained within an incoming XML message.
Once a client has been successfully authenticated, the Enterprise Gateway can insert a SAML authentication assertion into the downstream message.
Authenticate a user based on the username and password supplied in a WS-Security UsernameToken.
Insert a WS-Security Timestamp into a SOAP message.
Authenticate a client against CA's SOA Security Manager.