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

The
following
diagram
illustrates
this
solution
for
filtering
server-relative
URLs
See
also
“Handling
cookies
from
servers
across
multiple
-j
junctions”
on
page
295
and
“Processing
root
junction
requests”
on
page
294.
WebSEAL
provides
an
alternative,
non-cookie-based
solution
for
handling
dynamically
generated
server-relative
URLs.
See
“Handling
server-relative
URLs
with
junction
mapping”
on
page
293.
Handling
server-relative
URLs
with
junction
mapping
Server-relative
URLs
generated
on
the
client-side
by
applets
and
scripts
initially
lack
knowledge
of
the
junction
point.
WebSEAL
cannot
filter
the
URL
because
it
is
generated
on
the
client-side.
During
a
client
request
for
a
resource
using
this
URL,
WebSEAL
can
attempt
to
reprocess
the
server-relative
URL
using
junction
mapping.
Tivoli
Access
Manager
provides
an
alternative
to
the
cookie-based
solution
for
filtering
dynamically
generated
server-relative
URLs.
You
can
create
and
activate
a
junction
mapping
table
that
maps
specific
target
resources
to
junction
names.
WebSEAL
checks
the
location
information
in
the
server-relative
URL
with
the
data
contained
in
the
junction
mapping
table.
If
the
path
information
in
the
URL
matches
an
entry
in
the
table,
WebSEAL
directs
the
request
to
the
junction
associated
with
that
location.
The
table
is
an
ASCII
text
file
called
jmt.conf.
The
location
of
this
file
is
specified
in
the
[junction]
stanza
of
the
WebSEAL
configuration
file:
jmt-map
=
lib/jmt.conf
The
format
for
data
entry
in
the
table
consists
of
the
junction
name,
a
space,
and
the
resource
location
pattern.
You
can
also
use
wildcard
characters
to
express
the
resource
location
pattern.
In
the
following
example
of
the
junction
mapping
configuration
file,
two
back-end
servers
are
junctioned
to
WebSEAL
at
/jctA
and
/jctB:
#jmt.conf
#junction-name
resource-location-pattern
/jctA
/documents/release-notes.html
/jctA
/travel/index.html
/jctB
/accounts/*
/jctB
/images/weather/*.jpg
Client
WebSEAL
Application Server
(serves Javascript)
Script containing
server-relative URL:
/abc.html
/jctA
with -j option
Script runs and generates
link: /abc.html
request request
Client makes request
using link:
/abc.html
abc.html
successfully located
Cookie sent
with request
WebSEAL retries
request as:
/jctA/abc.html
1
2
3
/jctA
WebSEAL sends cookie
to identify junction
/jctA
Figure
14.
Processing
server-relative
URLs
Chapter
10.
WebSEAL
junctions
293