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.

Administrators<br />

can<br />

configure<br />

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

to<br />

insert<br />

a<br />

customized<br />

set<br />

of<br />

attributes<br />

into<br />

a<br />

failover<br />

cookie.<br />

Attributes<br />

can<br />

be<br />

specified<br />

individually<br />

or<br />

in<br />

a<br />

group.<br />

To<br />

specify<br />

a<br />

group<br />

of<br />

attributes,<br />

use<br />

wildcard<br />

pattern<br />

matching<br />

in<br />

configuration<br />

file<br />

entries.<br />

This<br />

feature<br />

is<br />

useful<br />

in<br />

deployments<br />

that<br />

also<br />

use<br />

customized<br />

authentication<br />

libraries,<br />

such<br />

as<br />

cross-domain<br />

authentication<br />

servers,<br />

to<br />

insert<br />

special<br />

attributes<br />

into<br />

a<br />

user<br />

credential.<br />

By<br />

specifying<br />

those<br />

attributes<br />

in<br />

the<br />

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

configuration<br />

file,<br />

the<br />

administrator<br />

can<br />

ensure<br />

that<br />

the<br />

attributes<br />

are<br />

available<br />

to<br />

add<br />

to<br />

the<br />

re-created<br />

user<br />

credential<br />

during<br />

failover<br />

authentication.<br />

Note:<br />

The<br />

maximum<br />

size<br />

of<br />

a<br />

failover<br />

authentication<br />

cookie<br />

is<br />

4<br />

kilobytes<br />

(4096<br />

bytes)<br />

Configuration<br />

instructions:<br />

v<br />

“Add<br />

the<br />

authentication<br />

level”<br />

on<br />

page<br />

176<br />

v<br />

“Add<br />

the<br />

session<br />

lifetime<br />

timestamp”<br />

on<br />

page<br />

176<br />

v<br />

“Add<br />

the<br />

session<br />

activity<br />

timestamp”<br />

on<br />

page<br />

176<br />

v<br />

“Add<br />

an<br />

interval<br />

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

updating<br />

the<br />

activity<br />

timestamp”<br />

on<br />

page<br />

177<br />

v<br />

“Add<br />

extended<br />

attributes”<br />

on<br />

page<br />

177<br />

Extraction<br />

of<br />

data<br />

from<br />

a<br />

failover<br />

cookie<br />

When<br />

a<br />

failover<br />

authentication<br />

event<br />

occurs,<br />

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

receives<br />

a<br />

failover<br />

authentication<br />

cookie<br />

and<br />

by<br />

default<br />

extracts<br />

the<br />

following<br />

data<br />

from<br />

each<br />

cookie:<br />

v<br />

User<br />

name<br />

v<br />

Authentication<br />

method<br />

v<br />

Cookie<br />

creation<br />

time<br />

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

first<br />

determines<br />

if<br />

the<br />

cookie<br />

is<br />

valid<br />

by<br />

subtracting<br />

the<br />

cookie<br />

creation<br />

time<br />

from<br />

the<br />

system<br />

time,<br />

and<br />

comparing<br />

this<br />

value<br />

against<br />

the<br />

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

configuration<br />

file<br />

entry<br />

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

failover<br />

cookie<br />

lifetime.<br />

If<br />

the<br />

cookie<br />

lifetime<br />

has<br />

been<br />

exceeded,<br />

the<br />

cookie<br />

is<br />

not<br />

valid,<br />

and<br />

failover<br />

authentication<br />

is<br />

not<br />

attempted.<br />

If<br />

the<br />

cookie<br />

lifetime<br />

has<br />

not<br />

been<br />

exceeded,<br />

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

uses<br />

the<br />

user<br />

name<br />

and<br />

authentication<br />

method<br />

to<br />

authenticate<br />

the<br />

user<br />

and<br />

build<br />

a<br />

user<br />

credential.<br />

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

next<br />

checks<br />

configuration<br />

settings<br />

to<br />

determine<br />

if<br />

additional<br />

cookie<br />

data<br />

should<br />

be<br />

extracted<br />

and<br />

evaluated.<br />

Note<br />

that<br />

the<br />

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

server<br />

does<br />

not<br />

by<br />

default<br />

extract<br />

any<br />

other<br />

attributes<br />

from<br />

the<br />

failover<br />

authentication<br />

cookie.<br />

Each<br />

additional<br />

attribute<br />

to<br />

be<br />

extracted<br />

must<br />

be<br />

specified<br />

in<br />

the<br />

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

configuration<br />

file.<br />

Wildcard<br />

pattern<br />

matching<br />

can<br />

be<br />

used<br />

to<br />

obtain<br />

groups<br />

of<br />

attributes.<br />

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

can<br />

be<br />

configured<br />

to<br />

extract<br />

the<br />

following<br />

defined<br />

attributes:<br />

v<br />

Authentication<br />

level<br />

When<br />

this<br />

value<br />

is<br />

extracted,<br />

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

uses<br />

it<br />

to<br />

ensure<br />

that<br />

the<br />

user<br />

is<br />

authenticated<br />

with<br />

the<br />

authentication<br />

method<br />

necessary<br />

to<br />

maintain<br />

the<br />

specified<br />

authentication<br />

level.<br />

Note<br />

that<br />

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

can<br />

obtain<br />

authentication<br />

levels<br />

from<br />

several<br />

different<br />

places:<br />

–<br />

Failover<br />

cookie<br />

–<br />

Failover<br />

authentication<br />

library<br />

–<br />

Cross-domain<br />

authentication<br />

service<br />

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