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