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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

[authentication-mechanisms]<br />

sso-create<br />

=<br />

/opt/pdwebrte/lib/libssocreate.so<br />

sso-consume<br />

=<br />

/opt/pdwebrte/lib/libssoconsume.so<br />

Windows:<br />

[authentication-mechanisms]<br />

sso-create<br />

=<br />

C:\Program<br />

Files\<strong>Tivoli</strong>\PDWebRTE\bin\ssocreate.dll<br />

sso-consume<br />

=<br />

C:\Program<br />

Files\<strong>Tivoli</strong>\PDWebRTE\bin\ssoconsume.dll<br />

3.<br />

Encrypting<br />

the<br />

authentication<br />

token<br />

data<br />

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

must<br />

encrypt<br />

the<br />

authentication<br />

data<br />

placed<br />

in<br />

the<br />

token<br />

using<br />

a<br />

key<br />

generated<br />

by<br />

the<br />

cdsso_key_gen<br />

utility.<br />

You<br />

must<br />

″synchronize″<br />

this<br />

key<br />

by<br />

sharing<br />

the<br />

key<br />

file<br />

with<br />

each<br />

participating<br />

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

server<br />

in<br />

each<br />

participating<br />

domain.<br />

Each<br />

participating<br />

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

server<br />

in<br />

each<br />

domain<br />

needs<br />

to<br />

use<br />

the<br />

same<br />

key.<br />

The<br />

generated<br />

key<br />

is<br />

a<br />

triple<br />

DES<br />

192<br />

bit<br />

key.<br />

You<br />

cannot<br />

specify<br />

a<br />

life<br />

span<br />

time<br />

on<br />

this<br />

key.<br />

Note:<br />

The<br />

distribution<br />

of<br />

key<br />

files<br />

is<br />

not<br />

a<br />

part<br />

of<br />

the<br />

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

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

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

CDSSO<br />

process.<br />

The<br />

cdsso_key_gen<br />

utility<br />

requires<br />

that<br />

you<br />

specify<br />

the<br />

location<br />

(absolute<br />

path<br />

name)<br />

of<br />

the<br />

key<br />

file<br />

when<br />

you<br />

run<br />

the<br />

utility.<br />

You<br />

must<br />

also<br />

use<br />

a<br />

full<br />

path<br />

name<br />

to<br />

run<br />

this<br />

utility:<br />

UNIX:<br />

#<br />

/opt/pdwebrte/bin/cdsso_key_gen<br />

<br />

Windows:<br />

MSDOS><br />

C:\Program<br />

Files\<strong>Tivoli</strong>\PDWebRTE\bin\cdsso_key_gen<br />

<br />

Enter<br />

this<br />

key<br />

file<br />

location<br />

in<br />

the<br />

[cdsso-peers]<br />

stanza<br />

of<br />

the<br />

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

configuration<br />

file<br />

of<br />

the<br />

participating<br />

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

server<br />

in<br />

each<br />

domain.<br />

The<br />

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

must<br />

include<br />

the<br />

fully<br />

qualified<br />

host<br />

name<br />

of<br />

the<br />

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

server<br />

and<br />

the<br />

absolute<br />

path<br />

name<br />

to<br />

the<br />

key<br />

file<br />

location:<br />

[cdsso-peers]<br />

<br />

=<br />

<br />

Configuration<br />

example<br />

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

server<br />

websealA<br />

in<br />

domain<br />

A:<br />

[cdsso-peers]<br />

websealB.domainB.com<br />

=<br />

/A-B.key<br />

This<br />

setting<br />

specifies<br />

what<br />

key<br />

websealA<br />

uses<br />

to<br />

encrypt<br />

a<br />

token<br />

destined<br />

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

websealB<br />

in<br />

domain<br />

B.<br />

Configuration<br />

example<br />

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

server<br />

websealB<br />

in<br />

domain<br />

B:<br />

[cdsso-peers]<br />

websealA.domainA.com<br />

=<br />

/A-B.key<br />

This<br />

setting<br />

specifies<br />

what<br />

key<br />

websealB<br />

(in<br />

domain<br />

B)<br />

uses<br />

to<br />

decrypt<br />

a<br />

token<br />

received<br />

from<br />

websealA<br />

in<br />

domain<br />

A.<br />

In<br />

the<br />

above<br />

example,<br />

the<br />

A-B.key<br />

file<br />

is<br />

generated<br />

on<br />

one<br />

machine<br />

(websealA,<br />

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

example)<br />

and<br />

manually<br />

(and<br />

securely)<br />

copied<br />

to<br />

the<br />

other<br />

machine<br />

(websealB,<br />

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

example).<br />

250<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!