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

ackwards
compatibility,
the
format
of
the
header
data
can
be
configured
to
raw
local
code
page.
In
addition,
two
other
formats
are
supported:
Raw
UTF-8
and
URI
encoded
local
code
page.
The
-e
option
for
creating
junctions
specifies
the
encoding
of
user
name,
groups,
and
other
extended
attributes
which
are
sent
within
the
HTTP
header
to
the
backend
server.
The
encode
option
can
take
one
of
the
following
arguments:
Argument
Description
utf8_uri
URI
encoded
UTF-8
data
All
white
space
and
non-ascii
bytes
are
encoded
%XY,
where
X
and
Y
are
hex
values
(0–F).
utf8_bin
Un-encoded
UTF-8
data.
This
setting
allows
data
to
be
transmitted
without
data
loss,
and
the
customer
does
not
need
to
URI-decode
the
data.
This
setting
should
be
used
with
caution,
because
it
is
not
part
of
the
HTTP
specification
lcp_uri
URI
encoded
local
code
page
data
Any
UTF-8
characters
which
can
not
be
converted
to
local
code
page
will
be
converted
to
question
marks
(
?
).
Use
this
option
with
caution
and
only
in
environments
where
local
code
page
produces
the
desired
strings.
lcp_bin
Un-encoded
local
code
page
data.
This
mode
was
used
by
versions
of
WebSEAL
prior
to
Version
5.1.
Use
of
this
mode
enables
migration
from
previous
versions,
and
is
used
in
upgrade
environments.
Note
that
data
loss
can
potentially
occur
with
this
mode.
Use
with
caution.
52
IBM
Tivoli
Access
Manager
for
e-business:
WebSEAL
Administration
Guide