IBM Tivoli Access Manager for e-business: WebSEAL Administration ...

Enable
or
disable
support
for
UTF-8
encoded
characters
in
query
strings
data
read
from
client
requests.
The
following
values
are
valid:
v
yes
WebSEAL
only
recognizes
UTF-8
encoding
in
strings
and
the
data
is
used
without
modification.
v
no
WebSEAL
does
not
recognize
UTF-8
encoding
in
strings.
Used
for
local
code
page
only.
v
auto
When
set
to
auto,
WebSEAL
attempts
to
distinguish
between
UTF-8
and
other
forms
of
language
character
encoding.
When
encoding
is
not
recognized
as
UTF-8,
WebSEAL
processes
the
string
as
non-UTF-8.
This
stanza
entry
is
required.
Default
value:
no
Example:
utf8-qstring-support-enabled
=
no
See
also
“Multi-locale
support
with
UTF-8”
on
page
44.
double-byte-encoding
=
{yes|no}
Specifies
whether
WebSEAL
will
assume
that
encoded
characters
within
URLs
are
always
encoded
in
Unicode,
and
do
not
contain
UTF-8
characters.
This
stanza
entry
is
required.
Default
value:
no
Example:
double-byte-encoding
=
no
suppress-server-identity
=
{yes|no}
Suppresses
the
identity
of
the
WebSEAL
server
from
HTTP
responses.
These
responses
normally
include
the
line:
Server:
WebSEAL/version_number
Setting
this
value
to
yes
deletes
the
above
line
from
the
server
response.
This
stanza
entry
is
required.
Default
value:
no
Example:
suppress-server-identity
=
no
pre-410–compatible-tokens
=
{yes|no}
WebSEAL
supports
a
common
method
of
generating
tokens
for
cross-domain
single
sign-on,
failover,
and
e-community
single
sign-on.
The
security
of
these
tokens
was
increased
for
Version
4.1.
This
increase
is
not
backwards
compatible
with
previous
versions
of
WebSEAL.
When
the
Tivoli
Access
Manager
deployment
includes
multiple
WebSEAL
servers,
and
some
of
the
WebSEAL
servers
are
Version
3.9
or
prior,
set
this
value
to
yes.
This
stanza
entry
is
required.
Default
value:
no
Example:
pre-410–compatible-tokens
=
no
390
IBM
Tivoli
Access
Manager
for
e-business:
WebSEAL
Administration
Guide