The HTTP Basic Authentication Trust Association Interceptor has
several configuration properties.
You can configure the following properties for the HTTP Basic
Authentication Trust Association Interceptor.
- enabled = ( false )
- Use this property to determine whether the TAI is active or not. Possible
values are true and false. The
default is false. If you set this property to true,
the TAI authenticates requests. If you set this property to false,
the TAI does not authenticate requests.
- loginTarget = ( Portal_LTPA )
- Use this property to specify the alias of the JAAS login configuration
that is used by the TAI. The default value is Portal_LTPA.
By this default, the TAI uses the same JAAS login configuration as the one
that is used by portal HTTP form based login.
- authenticationRealm = ( WPS )
- Use this property to specify the name of an authentication realm as defined
in RFC 2617. The TAI challenges the client to authenticate against this realm.
The default is WPS. By this default, the TAI uses the
same authentication realm name as the one that is used by portal HTTP form
based login.
- userAgentBlackList = ( * )
- Use this property to specify a list of patterns for which you do not want
the TAI to handle the requests. Separate the patterns by whitespaces.
Every
product name in the HTTP header field User-Agent of incoming
requests is compared with each of the patterns specified for this parameter.
If the TAI is enabled and the URL matches at least one of the patterns
specified for the userAgentBlackList property, the TAI will
not handle the request.
The default value is an asterisk
( * ); this default means that all patterns match,
and consequently the TAI handles no requests at all.
You
can specify the patterns with an asterisk ( * ) as
a wild card character. You can also define the patterns as Java regular expressions.
In this case set the property useRegExp (further
below) to true.
- urlBlackList = ( * )
- Use this property to specify a list of patterns for which you do not want
the TAI to handle the requests. Separate the patterns by whitespaces.
The
full path information of the URL of the incoming request is compared with
each of the patterns specified for this parameter. Before comparing the URL
to the patterns, the protocol, server, port, and query information is removed
from the URL. If the TAI is enabled and the URL matches at least one
of the patterns specified for the urlBlackList property,
the TAI will not handle the request.
The default value is an asterisk
( * ); this default means that all patterns match,
and consequently the TAI handles no requests at all.
Use the following syntax rules for specifying the patterns:
- You can use URI encoded patterns. For example, if you want to use the
blank character as part of a pattern, you can encode it as %20 .
It is then interpreted as part of the pattern and not as a pattern separator.
Make sure that you use only characters that are valid within a URI, and encode
all other characters.
- You can use an asterisk ( * ) as a wild card character.
- You can define the patterns as Java regular expressions. In this case
set the property useRegExp (further
below) to true.
- userAgentWhiteList = ( <your_pattern_here> )
- Use this property to specify a list of patterns for which you want the
TAI to handle the requests. Separate the patterns by whitespaces. Every product
name in the HTTP header field User-Agent of the incoming
request is compared with each of the patterns specified for this parameter.
If the TAI is enabled and the pattern specified for this
property has at least one match and neither of the userAgentBlackList or the urlBlackList have
a match, then the TAI handles the request.
The default
is <your_pattern_here> ; this
is not an actual value, but only a placeholder.
You
can specify the patterns with an asterisk ( * ) as
a wild card character. You can also define the patterns as Java regular expressions.
In this case set the property useRegExp (further
below) to true.
- urlWhiteList = ( <your_pattern_here> )
- Use this property to specify a list of patterns for which you want the
TAI to handle the requests. Separate the patterns by whitespaces. The full
path information of the URL of the incoming request is compared with each
of the patterns specified for this parameter. Before comparing the URL to
the patterns, the protocol, server, port, and query information is removed
from the URL.
If the TAI is enabled and the pattern specified for this
property has at least one match and neither of the userAgentBlackList or the urlBlackList have
a match, then the TAI handles the request.
The default
is <your_pattern_here> ; this
is not an actual value, but only a placeholder.
Use the following syntax rules for specifying the patterns:
- You can use URI encoded patterns. For example, if you want to use the
blank character as part of a pattern, you can encode it as %20 .
It is then interpreted as part of the pattern and not as a pattern separator.
Make sure that you use only characters that are valid within a URI, and encode
all other characters.
- You can use an asterisk ( * ) as a wild card character.
- You can define the patterns as Java regular expressions. In this case
set the property useRegExp (further
below) to true.