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

Create
a
new
junction
for
an
initial
server
Operation:
Creates
a
new
junction
point
and
junctions
an
initial
server.
Syntax:
create
-t
type
-h
host-name
[options]
junction-point
Junction
Type
–t
type
**Required**
Type
of
junction.
One
of:
tcp,
ssl,
tcpproxy,
sslproxy,
local.
Default
port
for
–t
tcp
is
80.
Default
port
for
–t
ssl
is
443.
Host
Name
–h
host-name
**Required**
The
DNS
host
name
or
IP
address
of
the
target
back-end
server.
Options
Mutual
Authentication
Over
SSL
–K
″key-label″
WebSEAL
uses
client
certificate
to
authenticate
to
back-end
server.
–B
WebSEAL
uses
BA
header
information
to
authenticate
to
back-end
server.
Requires
–U,
and
–W
options.
–U
″username″
WebSEAL
username.
Use
with
–B
to
send
BA
header
information
to
back-end
server.
–W
″password″
WebSEAL
password.
Use
with
–B
to
send
BA
header
information
to
back-end
server.
–D
″DN″
Specify
Distinguished
Name
of
back-end
server
certificate.
This
value,
matched
with
actual
certificate
DN
enhances
authentication.
Proxy
junction
options
(requires
–t
tcpproxy
or
–t
sslproxy)
–H
host-name
The
DNS
host
name
or
IP
address
of
the
proxy
server.
–P
port
The
TCP
port
of
the
proxy
server.
Supplying
BA
header
information
–b
BA-value
Defines
how
the
WebSEAL
server
passes
HTTP
BA
authentication
information
to
the
back-end
server.
One
of:
filter
(default),
ignore,
supply,
gso
General
TCP
and
SSL
junction
options
–c
id-types
Insert
Access
Manager
client
identity
in
HTTP
headers
across
the
junction.
The
id-types
argument
can
include
any
combination
of
the
following
Access
Manager
HTTP
header
types:
iv-user,
iv-user-l,
iv-groups,
iv-creds,
all.
–i
WebSEAL
server
treats
URLs
as
case
insensitive.
–j
Supply
junction
identification
in
a
cookie
to
handle
script
generated
server-relative
URLs.
–k
Send
session
cookie
to
back-end
portal
server.
Appendix
B.
WebSEAL
junction
reference
493