10.02.2013 Views

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 ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Configuring<br />

a<br />

basic<br />

<strong>WebSEAL</strong><br />

junction<br />

<strong>WebSEAL</strong><br />

supports<br />

both<br />

standard<br />

TCP<br />

(HTTP)<br />

and<br />

secure<br />

SSL<br />

(HTTPS)<br />

junctions<br />

between<br />

<strong>WebSEAL</strong><br />

and<br />

back-end<br />

Web<br />

application<br />

servers.<br />

The<br />

junction<br />

between<br />

<strong>WebSEAL</strong><br />

and<br />

the<br />

back-end<br />

server<br />

is<br />

independent<br />

of<br />

the<br />

type<br />

of<br />

connection<br />

(and<br />

its<br />

level<br />

of<br />

security)<br />

between<br />

the<br />

client<br />

and<br />

the<br />

<strong>WebSEAL</strong><br />

server.<br />

The<br />

mandatory<br />

command<br />

options<br />

required<br />

to<br />

create<br />

a<br />

basic<br />

<strong>WebSEAL</strong><br />

junction<br />

using<br />

pdadmin<br />

include:<br />

v<br />

Host<br />

name<br />

of<br />

the<br />

back-end<br />

application<br />

server<br />

(<br />

–h<br />

option)<br />

v<br />

Junction<br />

type:<br />

tcp,<br />

ssl,<br />

tcpproxy,<br />

sslproxy,<br />

local<br />

(<br />

–t<br />

option)<br />

v<br />

Junction<br />

point<br />

(mount<br />

point)<br />

pdadmin><br />

server<br />

task<br />

instance_name-webseald-host-name<br />

\<br />

create<br />

-t<br />

type<br />

-h<br />

host_name<br />

jct_point<br />

For<br />

example:<br />

pdadmin><br />

server<br />

task<br />

web1-webseald-cruz<br />

create<br />

-t<br />

tcp<br />

-h<br />

doc.tivoli.com<br />

/pubs<br />

Note:<br />

A<br />

″best<br />

practices″<br />

recommendation<br />

is<br />

to<br />

always<br />

use<br />

the<br />

fully<br />

qualified<br />

domain<br />

name<br />

of<br />

the<br />

back-end<br />

server<br />

when<br />

specifying<br />

the<br />

argument<br />

to<br />

the<br />

–h<br />

option.<br />

Creating<br />

TCP<br />

type<br />

junctions<br />

A<br />

<strong>WebSEAL</strong><br />

junction<br />

over<br />

a<br />

TCP<br />

connection<br />

provides<br />

the<br />

basic<br />

properties<br />

of<br />

a<br />

junction<br />

but<br />

does<br />

not<br />

provide<br />

secure<br />

communication<br />

across<br />

the<br />

junction.<br />

To<br />

create<br />

a<br />

secure<br />

TCP<br />

junction<br />

and<br />

add<br />

an<br />

initial<br />

server,<br />

use<br />

the<br />

create<br />

command<br />

with<br />

the<br />

–t<br />

tcp<br />

option:<br />

pdadmin><br />

server<br />

task<br />

webseald-instance-name<br />

create<br />

-t<br />

tcp<br />

-h<br />

host-name<br />

\<br />

[-p<br />

port]<br />

jct-point<br />

The<br />

default<br />

port<br />

value<br />

<strong>for</strong><br />

a<br />

TCP<br />

junction<br />

(if<br />

not<br />

specified)<br />

is<br />

80.<br />

Creating<br />

SSL<br />

type<br />

junctions<br />

SSL<br />

junctions<br />

function<br />

exactly<br />

like<br />

TCP<br />

junctions,<br />

with<br />

the<br />

added<br />

value<br />

that<br />

all<br />

communication<br />

between<br />

<strong>WebSEAL</strong><br />

and<br />

the<br />

back-end<br />

server<br />

is<br />

encrypted.<br />

SSL<br />

junctions<br />

allow<br />

secure<br />

end-to-end<br />

browser-to-application<br />

transactions.<br />

You<br />

can<br />

use<br />

SSL<br />

to<br />

secure<br />

communications<br />

from<br />

the<br />

client<br />

to<br />

<strong>WebSEAL</strong><br />

and<br />

from<br />

<strong>WebSEAL</strong><br />

to<br />

the<br />

back-end<br />

server.<br />

The<br />

back-end<br />

server<br />

must<br />

be<br />

HTTPS-enabled<br />

when<br />

you<br />

use<br />

an<br />

SSL<br />

junction.<br />

To<br />

create<br />

a<br />

secure<br />

SSL<br />

junction<br />

and<br />

add<br />

an<br />

initial<br />

server,<br />

use<br />

the<br />

create<br />

command<br />

with<br />

the<br />

–t<br />

ssl<br />

option:<br />

pdadmin><br />

server<br />

task<br />

instance_name-webseald-host-name<br />

create<br />

-t<br />

ssl<br />

-h<br />

host_name<br />

\<br />

[-p<br />

port]<br />

jct_point<br />

The<br />

default<br />

port<br />

value<br />

<strong>for</strong><br />

an<br />

SSL<br />

junction<br />

(if<br />

not<br />

specified)<br />

is<br />

443.<br />

Verifying<br />

the<br />

back-end<br />

server<br />

certificate<br />

When<br />

a<br />

client<br />

makes<br />

a<br />

request<br />

<strong>for</strong><br />

a<br />

resource<br />

on<br />

the<br />

back-end<br />

server,<br />

<strong>WebSEAL</strong>,<br />

in<br />

its<br />

role<br />

as<br />

a<br />

security<br />

server,<br />

per<strong>for</strong>ms<br />

the<br />

request<br />

on<br />

behalf<br />

of<br />

the<br />

client.<br />

The<br />

SSL<br />

280<br />

<strong>IBM</strong><br />

<strong>Tivoli</strong><br />

<strong>Access</strong><br />

<strong>Manager</strong><br />

<strong>for</strong><br />

e-<strong>business</strong>:<br />

<strong>WebSEAL</strong><br />

<strong>Administration</strong><br />

Guide

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!