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

support
(utf8-url-support-enabled)
and
forms
support
(utf8-forms-support-
enabled).
The
default
WebSEAL
setting
is
to
consume
data
in
UTF-8
format
only.
For
example,
the
need
to
change
default
settings
applies
to
administrators
running
systems
that
need
to
process
clients
requests
and
forms
data
use
non-UTF-8
local
code
pages,
such
as
those
for:
v
A
single-byte
Latin
character
set,
such
as
Spanish,
French,
or
German
v
A
multi-byte
character
set,
such
as
Japanese
or
Chinese
If
you
are
running
systems
that
need
to
provide
true
multi-locale
support
to
handle
users
and
data
in
multiple
languages,
you
should
review
your
local
code
page
setting
and
consider
converting
to
a
UTF-8
code
page.
Also
review
the
default
WebSEAL
multi-locale
UTF-8
settings.
You
might
want
to
customize
configuration
settings
to
best
fit
your
deployment.
UTF-8
dependency
on
user
registry
configuration
For
optimal
multi-locale
support,
all
users
should
be
stored
in
one
common
user
registry,
regardless
of
which
language
they
prefer.
Most
user
registries
support
UTF-8
by
default.
Some
LDAP
user
registries,
and
their
supporting
databases,
can
optionally
be
configured
to
not
support
UTF-8.
Ensure
that
the
LDAP
user
registry
and
database
used
with
Tivoli
Access
Manager
uses
UTF-8.
IBM
Directory
Services
is
by
default
configured
to
use
UTF-8.
UTF-8
data
conversion
issues
WebSEAL
can
be
deployed
into
environments
where
the
local
code
page
uses
UTF-8.
Similarly,
WebSEAL
can
also
be
deployed
into
environments
where
the
local
code
page
does
not
use
UTF-8.
The
use
of
Version
5.1
WebSEAL
with
operating
system
environments
that
use
non-UTF-8
local
code
pages
requires
WebSEAL
to
convert
data
upon
data
input
and
output.
When
WebSEAL
reads
data
in,
it
must
convert
the
data
from
non-UTF-8
to
UTF-8.
When
WebSEAL
writes
data
out,
it
must
convert
the
data
from
UTF-8
to
non-UTF-8.
If
conversion
to
a
local
code
page
is
required,
no
data
loss
will
occur
when
running
in
a
UTF-8
locale.
The
conversion
from
a
UTF-8
locale
to
a
non-UTF-8
locale
(local
code
page)
can,
in
some
situations,
result
in
data
loss.
Conversion
of
data
from
UTF-8
to
a
non-UTF-8
locale
can
result
in
data
loss.
For
example,
if
WebSEAL
is
running
in
an
en_US.ISO8859
environment,
and
a
Japanese
user
name
must
be
converted
to
the
local
code
page,
the
result
is
a
string
of
question
marks
(″????″).
This
occurs
because
there
is
no
way
to
represent
Japanese
characters
in
ISO-8859-1.
For
this
reason,
it
is
recommended
that
WebSEAL
is
run
using
UTF-8.
There
is
a
risk
of
data
loss
when
executing
administrative
commands
(pdadmin)
from
a
non-UTF-8
environment.
Prior
to
Version
5.1,
WebSEAL
always
ran
in
the
same
locale
as
the
pdadmin
utility.
With
multi-locale
support,
WebSEAL
can
now
run
in
a
different
locale.
WebSEAL
must
return
messages
to
the
administrator
in
the
administrator’s
chosen
language.
To
do
so,
WebSEAL
obtains
messages
from
the
appropriate
language
pack,
as
determined
by
the
locale
presented
by
pdadmin.
All
messages
are
transmitted
in
UTF-8,
but
pdadmin
converts
those
messages
to
local
code
page
prior
to
displaying
them.
When
the
local
code
page
is
non-UTF-8,
data
loss
is
potentially
possible.
When
pdadmin
is
run
in
a
UTF-8
environment,
there
will
be
no
data
loss.
Chapter
2.
WebSEAL
server
configuration
45