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.
When<br />
use-utf8<br />
is<br />
set<br />
to<br />
false,<br />
strings<br />
are<br />
encoded<br />
using<br />
the<br />
local<br />
code<br />
page.<br />
Use<br />
this<br />
value<br />
when<br />
implementing<br />
cross<br />
domain<br />
single<br />
sign-on<br />
with<br />
older<br />
(pre-Version<br />
5.1)<br />
<strong>WebSEAL</strong><br />
servers.<br />
<strong>WebSEAL</strong><br />
servers<br />
from<br />
versions<br />
prior<br />
to<br />
5.1<br />
do<br />
not<br />
use<br />
UTF-8<br />
encoding<br />
<strong>for</strong><br />
tokens.<br />
When<br />
deploying<br />
an<br />
environment<br />
that<br />
includes<br />
these<br />
older<br />
servers,<br />
configure<br />
the<br />
Version<br />
5.1<br />
<strong>WebSEAL</strong><br />
server<br />
to<br />
not<br />
use<br />
UTF-8<br />
encoding.<br />
This<br />
setting<br />
is<br />
necessary<br />
<strong>for</strong><br />
backwards<br />
compatibility.<br />
Note:<br />
Note<br />
that<br />
when<br />
this<br />
value<br />
is<br />
set<br />
to<br />
false,<br />
data<br />
loss<br />
can<br />
occur<br />
during<br />
conversion<br />
from<br />
UTF-8<br />
to<br />
a<br />
non-UTF-8<br />
local<br />
code<br />
page.<br />
UTF-8<br />
encoding<br />
of<br />
tokens<br />
<strong>for</strong><br />
e-community<br />
single<br />
sign-on<br />
The<br />
use<br />
of<br />
UTF-8<br />
encoding<br />
<strong>for</strong><br />
strings<br />
within<br />
tokens<br />
used<br />
<strong>for</strong><br />
e-community<br />
single<br />
sign-on<br />
is<br />
specified<br />
in<br />
the<br />
<strong>WebSEAL</strong><br />
configuration<br />
file.<br />
[e-community-sso]<br />
use-utf8<br />
=<br />
{yes|no}<br />
The<br />
default<br />
value<br />
is<br />
yes.<br />
When<br />
use-utf8<br />
is<br />
set<br />
to<br />
no,<br />
strings<br />
are<br />
encoded<br />
using<br />
the<br />
local<br />
code<br />
page.<br />
Use<br />
this<br />
value<br />
when<br />
implementing<br />
e-community<br />
single<br />
sign-on<br />
with<br />
older<br />
(pre-Version<br />
5.1)<br />
<strong>WebSEAL</strong><br />
servers.<br />
<strong>WebSEAL</strong><br />
servers<br />
from<br />
versions<br />
prior<br />
to<br />
5.1<br />
do<br />
not<br />
use<br />
UTF-8<br />
encoding<br />
<strong>for</strong><br />
tokens.<br />
When<br />
deploying<br />
an<br />
environment<br />
that<br />
includes<br />
these<br />
older<br />
servers,<br />
configure<br />
the<br />
Version<br />
5.1<br />
<strong>WebSEAL</strong><br />
server<br />
to<br />
not<br />
use<br />
UTF-8<br />
encoding.<br />
This<br />
setting<br />
is<br />
necessary<br />
<strong>for</strong><br />
backwards<br />
compatibility.<br />
Note:<br />
Note<br />
that<br />
when<br />
this<br />
value<br />
is<br />
set<br />
to<br />
no,<br />
data<br />
loss<br />
can<br />
occur<br />
during<br />
conversion<br />
from<br />
UTF-8<br />
to<br />
a<br />
non-UTF-8<br />
local<br />
code<br />
page.<br />
UTF-8<br />
encoding<br />
of<br />
cookies<br />
<strong>for</strong><br />
failover<br />
authentication<br />
The<br />
use<br />
of<br />
UTF-8<br />
encoding<br />
<strong>for</strong><br />
strings<br />
within<br />
failover<br />
authentication<br />
cookies<br />
is<br />
specified<br />
in<br />
the<br />
<strong>WebSEAL</strong><br />
configuration<br />
file.<br />
[failover]<br />
use-utf8<br />
=<br />
{yes|no}<br />
The<br />
default<br />
value<br />
is<br />
yes.<br />
When<br />
use-utf8<br />
is<br />
set<br />
to<br />
no,<br />
failover<br />
authentication<br />
cookies<br />
are<br />
encoded<br />
using<br />
the<br />
local<br />
code<br />
page.<br />
Use<br />
this<br />
value<br />
when<br />
implementing<br />
failover<br />
authentication<br />
with<br />
older<br />
(pre-Version<br />
5.1)<br />
<strong>WebSEAL</strong><br />
servers.<br />
<strong>WebSEAL</strong><br />
servers<br />
from<br />
versions<br />
prior<br />
to<br />
5.1<br />
do<br />
not<br />
use<br />
UTF-8<br />
encoding<br />
<strong>for</strong><br />
failover<br />
authentication<br />
cookies.<br />
When<br />
deploying<br />
an<br />
environment<br />
that<br />
includes<br />
these<br />
older<br />
servers,<br />
configure<br />
the<br />
Version<br />
5.1<br />
<strong>WebSEAL</strong><br />
server<br />
to<br />
not<br />
use<br />
UTF-8<br />
encoding.<br />
This<br />
setting<br />
is<br />
necessary<br />
<strong>for</strong><br />
backwards<br />
compatibility.<br />
Note:<br />
Note<br />
that<br />
when<br />
this<br />
value<br />
is<br />
set<br />
to<br />
no,<br />
data<br />
loss<br />
can<br />
occur<br />
during<br />
conversion<br />
from<br />
UTF-8<br />
to<br />
a<br />
non-UTF-8<br />
local<br />
code<br />
page.<br />
UTF-8<br />
encoding<br />
in<br />
junction<br />
requests<br />
<strong>WebSEAL</strong><br />
inserts<br />
in<strong>for</strong>mation<br />
into<br />
HTTP<br />
headers<br />
<strong>for</strong><br />
requests<br />
to<br />
the<br />
backend<br />
server.<br />
This<br />
in<strong>for</strong>mation<br />
can<br />
include<br />
extended<br />
attributes<br />
or<br />
user<br />
data.<br />
In<br />
<strong>WebSEAL</strong><br />
versions<br />
prior<br />
to<br />
5.1,<br />
the<br />
headers<br />
were<br />
added<br />
to<br />
the<br />
request<br />
using<br />
raw<br />
local<br />
code<br />
page.<br />
In<br />
Version<br />
5.1,<br />
the<br />
header<br />
data<br />
is<br />
transmitted<br />
in<br />
a<br />
configurable<br />
<strong>for</strong>mat.<br />
By<br />
default,<br />
<strong>WebSEAL</strong><br />
now<br />
adds<br />
in<strong>for</strong>mation<br />
to<br />
HTTP<br />
headers<br />
using<br />
a<br />
UTF-8<br />
code<br />
page.<br />
This<br />
prevents<br />
any<br />
potential<br />
data<br />
loss<br />
that<br />
could<br />
occur<br />
when<br />
converting<br />
to<br />
a<br />
non-UTF-8<br />
code<br />
page.<br />
Also<br />
by<br />
default,<br />
this<br />
data<br />
is<br />
sent<br />
URI<br />
encoded.<br />
For<br />
Chapter<br />
2.<br />
<strong>WebSEAL</strong><br />
server<br />
configuration<br />
51
Change language