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.

The<br />

session<br />

cache<br />

entry<br />

lifetime<br />

value<br />

usually<br />

determines<br />

the<br />

maximum<br />

session<br />

length.<br />

When<br />

this<br />

lifetime<br />

value<br />

expires,<br />

the<br />

session<br />

is<br />

normally<br />

terminated<br />

regardless<br />

of<br />

activity.<br />

However,<br />

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

can<br />

be<br />

configured<br />

to<br />

allow<br />

the<br />

user<br />

to<br />

reauthenticate<br />

after<br />

the<br />

session<br />

lifetime<br />

value<br />

has<br />

expired.<br />

After<br />

successful<br />

reauthentication,<br />

the<br />

lifetime<br />

value<br />

of<br />

the<br />

session<br />

cache<br />

entry<br />

is<br />

reset.<br />

Two<br />

other<br />

conditions<br />

can<br />

end<br />

a<br />

user<br />

session:<br />

the<br />

user<br />

can<br />

explicitly<br />

log<br />

out<br />

or<br />

an<br />

administrator<br />

can<br />

terminate<br />

a<br />

user<br />

session.<br />

See<br />

“Terminating<br />

user<br />

sessions”<br />

on<br />

page<br />

345.<br />

Configuration<br />

is<br />

available<br />

to<br />

reset<br />

the<br />

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

session<br />

cache<br />

entry<br />

lifetime<br />

timer.<br />

In<br />

addition,<br />

a<br />

grace<br />

period<br />

can<br />

be<br />

configured<br />

to<br />

allow<br />

sufficient<br />

time<br />

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

the<br />

reauthentication<br />

process<br />

to<br />

complete<br />

be<strong>for</strong>e<br />

the<br />

lifetime<br />

timeout<br />

of<br />

the<br />

session<br />

cache<br />

entry<br />

expires.<br />

Enabling<br />

inactivity<br />

reauthentication<br />

To<br />

configure<br />

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

to<br />

″flag″<br />

inactive<br />

sessions<br />

rather<br />

than<br />

remove<br />

them<br />

from<br />

the<br />

session<br />

cache,<br />

set<br />

the<br />

value<br />

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

the<br />

reauth-<strong>for</strong>-inactive<br />

parameter<br />

to<br />

″yes″<br />

in<br />

the<br />

[reauthentication]<br />

stanza<br />

of<br />

the<br />

webseald.conf<br />

configuration<br />

file:<br />

[reauthentication]<br />

reauth-<strong>for</strong>-inactive<br />

=<br />

yes<br />

The<br />

default<br />

value<br />

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

this<br />

parameter<br />

is<br />

″no″.<br />

Resetting<br />

and<br />

extending<br />

the<br />

session<br />

cache<br />

entry<br />

lifetime<br />

value<br />

Resetting<br />

the<br />

session<br />

cache<br />

entry<br />

lifetime<br />

value<br />

The<br />

user’s<br />

session<br />

cache<br />

entry<br />

has<br />

a<br />

limited<br />

lifetime,<br />

as<br />

specified<br />

by<br />

the<br />

timeout<br />

parameter<br />

in<br />

the<br />

[session]<br />

stanza<br />

of<br />

the<br />

webseald.conf<br />

configuration<br />

file.<br />

The<br />

default<br />

value,<br />

in<br />

seconds,<br />

is<br />

3600<br />

(1<br />

hour):<br />

[session]<br />

timeout<br />

=<br />

3600<br />

Regardless<br />

of<br />

session<br />

activity<br />

or<br />

inactivity,<br />

the<br />

session<br />

cache<br />

entry<br />

is<br />

removed<br />

when<br />

the<br />

lifetime<br />

value<br />

is<br />

reached,<br />

at<br />

which<br />

point<br />

the<br />

user<br />

is<br />

logged<br />

off.<br />

However,<br />

you<br />

can<br />

configure<br />

the<br />

lifetime<br />

of<br />

the<br />

session<br />

cache<br />

entry<br />

to<br />

be<br />

reset<br />

whenever<br />

reauthentication<br />

occurs.<br />

With<br />

this<br />

configuration,<br />

the<br />

user<br />

session<br />

no<br />

longer<br />

has<br />

a<br />

single<br />

maximum<br />

lifetime<br />

value.<br />

Each<br />

time<br />

reauthentication<br />

occurs,<br />

the<br />

session<br />

cache<br />

entry<br />

lifetime<br />

value<br />

is<br />

reset.<br />

You<br />

can<br />

reset<br />

the<br />

lifetime<br />

value<br />

of<br />

session<br />

cache<br />

entries<br />

with<br />

the<br />

reauth-reset-lifetime<br />

parameter<br />

in<br />

the<br />

[reauthentication]<br />

stanza<br />

of<br />

the<br />

webseald.conf<br />

configuration<br />

file:<br />

[reauthentication]<br />

reauth-reset-lifetime<br />

=<br />

yes<br />

The<br />

default<br />

value<br />

is<br />

″no″.<br />

This<br />

parameter<br />

is<br />

also<br />

appropriate<br />

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

reauthentication<br />

due<br />

security<br />

(POP)<br />

policy.<br />

See<br />

“Configuring<br />

reauthentication<br />

based<br />

on<br />

security<br />

policy”<br />

on<br />

page<br />

204.<br />

Chapter<br />

7.<br />

Advanced<br />

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

authentication<br />

209

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

Saved successfully!

Ooh no, something went wrong!