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

WebSEAL
does
not
recognize
UTF-8
encoding
in
forms.
Used
for
local
code
page
only.
If
the
form
data
can
be
validated
it
is
converted
to
UTF-8
for
internal
use.
v
auto
WebSEAL
attempts
to
distinguish
between
UTF-8
and
other
forms
of
language
character
encoding.
WebSEAL
correctly
processes
any
correctly
constructed
UTF-8
input.
If
the
encoding
does
not
appear
to
be
UTF-8,
then
the
coding
is
processed
as
non-UTF-8.
UTF-8
support
in
query
strings
The
manner
in
which
WebSEAL
processes
data
from
query
strings
can
be
specified
in
the
WebSEAL
configuration
file:
[server]
utf8-qstring-support-enabled
=
{yes|no|enabled}
The
default
setting
is
no.
Thus,
WebSEAL
default
behavior
is
to
assume
all
query
strings
are
local
code
page.
The
three
possible
values
are
as
follows:
v
yes
WebSEAL
only
recognizes
UTF-8
encoding
in
query
strings
and
the
data
is
used
without
modification.
These
UTF-8
characters
are
then
validated
and
taken
into
account
when
processing
the
data.
Other
encoding
techniques
are
not
accepted.
Use
this
setting
when
your
WebSEAL
server
must
process
query
strings
that
use
UTF-8.
Servers
that
operate
in
an
single-byte
Latin
locale,
such
as
French,
German,
or
Spanish,
and
process
queries
from
an
application
that
uses
UTF-8,
should
use
this
setting.
Servers
that
operate
in
a
multi-byte
locale
and
process
only
UTF-8
query
strings
can
use
this
setting.
v
no
WebSEAL
does
not
recognize
UTF-8
encoding
in
query
string.
Used
for
local
code
page
only.
If
the
form
data
can
be
validated
it
is
converted
to
UTF-8
for
internal
use.
This
is
the
default
value,
and
is
recommended.
Servers
that
operate
in
a
7-bit
ASCII
English
locale
can
use
this
setting.
v
auto
WebSEAL
attempts
to
distinguish
between
UTF-8
and
other
forms
of
language
character
encoding
(DBCS
and
Unicode).
WebSEAL
correctly
processes
any
correctly
constructed
UTF-8
encoding.
If
the
encoding
does
not
appear
to
be
UTF-8,
then
the
coding
is
processed
as
DBCS
or
Unicode.
Servers
that
operate
in
a
multi-byte
locale
and
process
a
mixture
of
UTF-8
and
non-UTF-8
query
strings
can
use
this
setting.
Servers
that
operate
in
an
single-byte
Latin
locale,
such
as
French,
German,
or
Spanish,
and
process
a
mixture
of
UTF-8
and
non-UTF-8
query
strings
can
use
this
setting.
UTF-8
encoding
of
tokens
for
cross
domain
single
sign-on
The
use
of
UTF-8
encoding
for
strings
within
tokens
used
for
cross
domain
single
sign-on
is
specified
in
the
WebSEAL
configuration
file.
[cdsso]
use-utf8
=
{true|false}
The
default
value
is
true.
50
IBM
Tivoli
Access
Manager
for
e-business:
WebSEAL
Administration
Guide