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.

4.<br />

Configuring<br />

the<br />

token<br />

time<br />

stamp<br />

The<br />

token<br />

contains<br />

a<br />

configurable<br />

time<br />

stamp<br />

that<br />

defines<br />

the<br />

lifetime<br />

of<br />

the<br />

identity<br />

token.<br />

After<br />

the<br />

time<br />

stamp<br />

has<br />

expired,<br />

the<br />

token<br />

is<br />

considered<br />

invalid<br />

and<br />

is<br />

not<br />

used.<br />

The<br />

time<br />

stamp<br />

is<br />

used<br />

to<br />

help<br />

prevent<br />

replay<br />

attacks<br />

by<br />

setting<br />

a<br />

value<br />

short<br />

enough<br />

to<br />

prevent<br />

the<br />

token<br />

from<br />

being<br />

stolen<br />

and<br />

replayed<br />

within<br />

its<br />

lifetime.<br />

The<br />

authtoken-lifetime<br />

parameter,<br />

located<br />

in<br />

the<br />

[cdsso]<br />

stanza<br />

of<br />

the<br />

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

configuration<br />

file,<br />

sets<br />

the<br />

token<br />

lifetime<br />

value.<br />

The<br />

value<br />

is<br />

expressed<br />

in<br />

seconds.<br />

The<br />

default<br />

value<br />

is<br />

180:<br />

[cdsso]<br />

authtoken-lifetime<br />

=<br />

180<br />

You<br />

must<br />

take<br />

into<br />

account<br />

any<br />

clock<br />

skew<br />

among<br />

the<br />

participating<br />

domains.<br />

Clock<br />

skew<br />

means<br />

that<br />

the<br />

system<br />

times<br />

differ<br />

on<br />

the<br />

relevant<br />

servers<br />

in<br />

each<br />

domain.<br />

When<br />

this<br />

difference<br />

approaches<br />

the<br />

value<br />

of<br />

authtoken-lifetime,<br />

the<br />

effective<br />

lifetime<br />

of<br />

the<br />

token<br />

is<br />

greatly<br />

reduced.<br />

When<br />

this<br />

difference<br />

exceeds<br />

the<br />

value<br />

of<br />

authtoken-lifetime,<br />

tokens<br />

from<br />

one<br />

domain<br />

cannot<br />

be<br />

valid<br />

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

the<br />

other<br />

domain.<br />

Administrators<br />

should<br />

adjust<br />

authtoken-lifetime<br />

accordingly.<br />

However,<br />

when<br />

clock<br />

skew<br />

requires<br />

that<br />

authtoken-lifetime<br />

be<br />

set<br />

to<br />

a<br />

large<br />

value,<br />

the<br />

risk<br />

of<br />

replay<br />

attacks<br />

increases.<br />

In<br />

this<br />

case,<br />

administrators<br />

should<br />

consider<br />

synchronizing<br />

the<br />

system<br />

time<br />

on<br />

the<br />

relevant<br />

servers<br />

in<br />

each<br />

domain.<br />

See<br />

“Cross-domain<br />

single<br />

sign-on”<br />

on<br />

page<br />

428.<br />

5.<br />

Configuring<br />

the<br />

token<br />

label<br />

name<br />

The<br />

authentication<br />

in<strong>for</strong>mation<br />

used<br />

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

a<br />

single<br />

sign-on<br />

transaction<br />

is<br />

placed<br />

in<br />

the<br />

redirected<br />

request<br />

as<br />

an<br />

encrypted<br />

token<br />

query<br />

string<br />

argument<br />

to<br />

the<br />

request.<br />

This<br />

token<br />

string<br />

requires<br />

a<br />

name,<br />

or<br />

label,<br />

to<br />

identify<br />

it.<br />

The<br />

label<br />

name<br />

uniquely<br />

identifies<br />

the<br />

request<br />

to<br />

the<br />

receiving<br />

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

server<br />

as<br />

a<br />

single<br />

sign-on<br />

request<br />

to<br />

be<br />

handled<br />

by<br />

the<br />

CDSSO<br />

token<br />

consume<br />

mechanism<br />

(library).<br />

You<br />

must<br />

configure<br />

this<br />

token<br />

label<br />

identically<br />

on<br />

both<br />

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

servers<br />

participating<br />

in<br />

the<br />

single<br />

sign-on<br />

functionality.<br />

To<br />

configure<br />

the<br />

token<br />

label,<br />

use<br />

the<br />

cdsso-argument<br />

parameter<br />

located<br />

in<br />

the<br />

[cdsso]<br />

stanza<br />

of<br />

the<br />

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

configuration<br />

file.<br />

For<br />

example<br />

(default):<br />

[cdsso]<br />

cdsso-argument<br />

=<br />

PD-ID<br />

See<br />

“Cross-domain<br />

single<br />

sign-on”<br />

on<br />

page<br />

428.<br />

Creating<br />

the<br />

CDSSO<br />

HTML<br />

link<br />

The<br />

HTML<br />

link<br />

(located<br />

on<br />

the<br />

original<br />

server)<br />

that<br />

connects<br />

the<br />

user<br />

to<br />

a<br />

resource<br />

on<br />

the<br />

destination<br />

server<br />

must<br />

use<br />

a<br />

special<br />

CDSSO<br />

expression<br />

that<br />

directs<br />

the<br />

request<br />

to<br />

a<br />

CDSSO<br />

management<br />

page<br />

pkmscdsso:<br />

/pkmscdsso?<br />

For<br />

example:<br />

http://websealA/pkmscdsso?https://websealB/resource.html<br />

The<br />

token<br />

create<br />

library<br />

creates<br />

and<br />

encodes<br />

an<br />

authentication<br />

token<br />

(containing<br />

the<br />

user’s<br />

identity<br />

in<strong>for</strong>mation)<br />

and<br />

includes<br />

this<br />

token<br />

in<br />

a<br />

redirected<br />

request<br />

to<br />

the<br />

resource<br />

using<br />

the<br />

destination<br />

URL<br />

in<strong>for</strong>mation<br />

from<br />

the<br />

CDSSO<br />

link.<br />

For<br />

example:<br />

Chapter<br />

9.<br />

Client<br />

single<br />

sign-on<br />

solutions<br />

251

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

Saved successfully!

Ooh no, something went wrong!