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

Multi-locale
support
with
UTF-8
This
section
consists
of
the
following
topics:
v
“Multi-locale
support
concepts”
v
“Configuring
multi-locale
support”
on
page
48
Multi-locale
support
concepts
This
section
contains
the
following
topics:
v
“WebSEAL
data
handling
using
UTF-8”
v
“UTF-8
dependency
on
user
registry
configuration”
on
page
45
v
“UTF-8
data
conversion
issues”
on
page
45
v
“UTF-8
environment
variables
for
CGI
programs”
on
page
46
v
“UTF-8
impact
on
authentication”
on
page
46
v
“URLs
must
use
only
one
encoding
type”
on
page
47
v
“UTF-8
support
during
WebSEAL
upgrade”
on
page
47
WebSEAL
data
handling
using
UTF-8
WebSEAL
Version
5.1
support
multiple
locales.
This
support
enables
WebSEAL
to
process
data
from
multiple
languages
at
once.
WebSEAL
implements
multi-locale
support
by
internally
maintaining
and
handling
all
data
using
UCS
Transformation
Format
8
byte
(UTF-8)
encoding
.
UTF-8
is
a
multi-byte
code
page
with
variable
width.
Prior
versions
of
WebSEAL
provided
limited
multi-locale
support.
While
WebSEAL
could
support
a
variety
of
languages
as
requested
by
a
browser
(client),
WebSEAL
could
support
only
one
language
at
a
tine.
In
Version
5.1,
WebSEAL
adopts
UTF-8
as
the
default
code
page
for
all
internal
data
handling.
WebSEAL
administrators
can
configure
how
WebSEAL
handles
data
input
and
output.
An
example
of
data
input
is
characters
sent
to
WebSEAL
by
a
browser,
such
as
user
logins
and
forms
data.
An
example
of
data
output
is
logging
information
written
out
to
the
filesystem
by
the
Tivoli
Access
Manager
event
logging
manager.
The
change
within
WebSEAL
to
use
UTF-8
should
be
transparent
to
administrators
whose
systems
do
not
need
to
provide
multi-locale
(and
multiple
language)
supports.
WebSEAL
handles
data
internally
in
UTF-8
regardless
of
the
locale
in
which
the
WebSEAL
process
is
running.
When
locale-specific
data
is
needed
as
input
or
output,
the
locale
in
which
the
WebSEAL
process
is
running
becomes
important.
Note
that
most
operating
systems
do
not
use
UTF-8
by
default.
Administrators
expecting
locale-specific
behavior
need
to
know
which
locale
is
being
used,
and
need
to
set
WebSEAL
UTF-8
configuration
options
to
match
the
required
behavior.
The
system
locale
consists
of
two
parts:
the
language
and
the
local
code
page.
Local
code
pages
can
by
UTF-8
or
not
UTF-8.
Historically,
most
operating
systems
use
a
local
code
page
that
is
not
UTF-8.
For
example,
a
common
local
code
page
used
to
represent
the
8-bit
ASCII
character
set
for
United
States
English
is
en_US.ISO88591,
which
uses
the
ISO-8859-1
character
set.
Administrators
running
systems
that
need
to
process
client
requests
and
forms
data
in
the
local
code
page
will
want
to
modify
the
default
settings
for
URL
44
IBM
Tivoli
Access
Manager
for
e-business:
WebSEAL
Administration
Guide