The HTTP Basic Authentication Trust Association Interceptor

 

+

Search Tips   |   Advanced Search

 

The HTTP Basic Authentication Trust Association Interceptor (TAI) can be used to authenticate incoming requests using the HTTP Basic Authentication Protocol described in RFC 2617. This can be useful for clients that are not capable of doing HTTP FORM based authentication.

In general, HTTP Basic Authentication has the following two main disadvantages compared to HTTP Form based authentication:

If the HTTP Basic Authentication TAI is enabled, it decides on every incoming request whether it is responsible for the authentication of that request or not. This decision is based on black and white lists for the requested URL and the client's user agent. The TAI is responsible only if none of the patterns in the black lists match and at least one of the patterns in one of the white lists match. Therefore, if the TAI is configured with empty white lists, it will never authenticate a request.

If the TAI decides to authenticate the request and that request contains an authorization header that contains a user ID and password, the TAI tries to log on with that credential. If no user ID and password is provided, the TAI will challenge the client according to RFC 2617.


Parent topic:

Enable HTTP Basic Authentication for simple clients


Related concepts


HTTP Basic Authentication Trust Association Interceptor in combination with external authentication servers


Related tasks


Configure the HTTP Basic Authentication Trust Association Interceptor


Related reference


Reference: Properties for the Trust Association Interceptor