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

Configuring
multi-locale
support
Configuration
topics
for
multi-locale
support:
v
“UTF-8
support
for
uniform
resource
locators”
v
“UTF-8
support
for
forms”
on
page
49
v
“UTF-8
support
in
query
strings”
on
page
50
v
“UTF-8
encoding
of
tokens
for
cross
domain
single
sign-on”
on
page
50
v
“UTF-8
encoding
of
tokens
for
e-community
single
sign-on”
on
page
51
v
“UTF-8
encoding
of
cookies
for
failover
authentication”
on
page
51
v
“UTF-8
encoding
in
junction
requests”
on
page
51
UTF-8
support
for
uniform
resource
locators
Browsers
are
limited
to
a
defined
character
set
that
can
legally
be
used
within
a
Uniform
Resource
Locator
(URL).
This
range
is
defined
to
be
the
printable
characters
in
the
ASCII
character
set
(between
hex
code
0x20
and
0x7e).
For
non-English
languages,
and
other
purposes,
characters
outside
the
printable
ASCII
character
set
are
often
required
in
URLs.
These
characters
can
be
encoded
using
printable
characters
for
transmission
and
interpretation.
There
are
a
number
of
different
encoding
methods
for
transmitting
characters
outside
the
printable
ASCII
range.
WebSEAL,
acting
as
a
Web
proxy,
must
be
able
to
handle
all
these
cases.
The
UTF-8
locale
support
addresses
this
need.
The
manner
in
which
WebSEAL
processes
URLs
from
browsers
can
be
specified
in
the
WebSEAL
configuration
file:
[server]
utf8-url-support-enabled
=
{yes|no|auto}
The
three
possible
values
are
as
follows:
v
yes
In
this
mode,
WebSEAL
only
recognizes
URI
encoded
UTF-8
data
in
URL
strings
and
they
are
used
without
modification.
These
UTF-8
characters
are
then
validated
and
taken
into
account
when
determining
access
rights
to
the
URL.
WebSEAL
supports
both
raw
UTF-8
and
URI
encoded
UTF-8
strings
in
URLs.
In
this
mode,
other
encoding
techniques
are
not
accepted.
This
is
the
default
value,
and
is
recommended.
Servers
that
run
in
an
7-bit
ASCII
English
locale
should
use
this
value.
v
no
In
this
mode,
WebSEAL
does
not
recognize
UTF-8
format
data
in
URL
strings.
Used
for
local
code
page
only.
If
the
string
can
be
validated
it
is
converted
to
UTF-8
for
internal
use.
Servers
that
do
not
need
to
process
multi-byte
input,
and
are
running
in
a
single-byte
Latin
locale,
such
as
French,
German,
or
Spanish,
should
use
this
setting.
Use
this
setting
when
supporting
existing
applications
and
Web
servers
do
not
function
correctly
with
WebSEAL
if
UTF-8
support
is
enabled.
These
applications
might
use
DBCS
(such
as
Shift-JIS)
or
other
encoding
mechanisms
in
the
URL.
Note:
When
setting
this
value
to
no,
ensure
that
all
junctioned
servers
do
NOT
accept
UTF-8
format
URLs.
It
is
important
from
a
security
perspective,
that
WebSEAL
interprets
URLs
in
the
same
manner
as
the
junctioned
servers.
v
auto
48
IBM
Tivoli
Access
Manager
for
e-business:
WebSEAL
Administration
Guide