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

″_UTF8″
appended
to
the
end.
The
values
of
these
variables
are
URI
(Uniform
Resource
Indicator)
encoded
UTF-8
strings.
URI
encoding
is
used
to
prevent
data
loss
on
platforms
which
expect
local
code
page
environment
variables
in
spawned
processes.
The
variables
are:
v
REMOTE_USER_UTF8
v
IV_USER_UTF8
v
HTTP_IV_USER_UTF8
v
IV_GROUPS_UTF8
v
HTTP_IV_GROUPS_UTF8
New
CGI
programs
should
use
these
variables
because
their
values
contain
UTF-8
data.
WebSEAL
stores
the
data
for
these
variables
internally
in
UTF-8
format.
The
data
must
be
converted
to
local
code
page
in
order
for
CGI
programs
to
use
it.
When
the
old
CGI
variables
(
for
example,
REMOTE_USER)
are
used,
and
the
local
code
page
is
not
UTF-8
encoded,
the
conversion
of
the
UTF-8
data
to
the
local
code
page
can,
in
some
cases,
result
in
data
corruption.
Windows:
Supporting
WIN32
environment
variables
This
section
applies
to
local
junctions
only.
Windows
does
not
automatically
make
all
of
its
system
environment
variables
available
to
processes
such
as
CGI
applications.
Typically,
the
system
environment
variables
you
require
are
present.
However,
if
any
Windows
system
environment
variables
that
you
require
are
not
present
in
the
CGI
environment,
you
can
explicitly
make
them
available
to
CGI
programs
through
the
WebSEAL
configuration
file.
(Note
that
the
Tivoli
Access
Manager
environment
variables
mentioned
in
the
previous
section
are
automatically
available
on
all
platforms).
Add
any
of
the
required
Windows
system
environment
variables
to
the
[cgi-environment-variables]
stanza
of
the
WebSEAL
configuration
file.
Use
the
following
format:
ENV
=
variable_name
For
example:
[cgi-environment-variables]
#ENV
=
SystemDrive
ENV
=
SystemRoot
ENV
=
PATH
ENV
=
LANG
ENV
=
LC_ALL
ENV
=
LC_CTYPE
ENV
=
LC_MESSAGES
ENV
=
LOCPATH
ENV
=
NLSPATH
Any
uncommented
lines
are
inherited
by
a
CGI
environment.
Chapter
12.
Application
integration
337