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.

The<br />

GSKit<br />

cache<br />

also<br />

maintains<br />

session<br />

state<br />

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

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

the<br />

SSL<br />

connection<br />

between<br />

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

and<br />

the<br />

LDAP<br />

user<br />

registry.<br />

Configuring<br />

the<br />

GSKit<br />

SSL<br />

session<br />

ID<br />

cache<br />

The<br />

following<br />

configuration<br />

tasks<br />

are<br />

available<br />

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

the<br />

GSKit<br />

SSL<br />

session<br />

ID<br />

cache:<br />

v<br />

Setting<br />

the<br />

cache<br />

entry<br />

timeout<br />

value<br />

v<br />

Setting<br />

the<br />

maximum<br />

concurrent<br />

entries<br />

value<br />

Setting<br />

the<br />

cache<br />

entry<br />

timeout<br />

value<br />

The<br />

parameters<br />

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

setting<br />

the<br />

maximum<br />

lifetime<br />

timeout<br />

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

an<br />

entry<br />

in<br />

the<br />

GSKit<br />

SSL<br />

session<br />

ID<br />

cache<br />

are<br />

located<br />

in<br />

the<br />

[ssl]<br />

stanza<br />

of<br />

the<br />

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

configuration<br />

file.<br />

There<br />

are<br />

two<br />

parameters:<br />

one<br />

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

SSL<br />

V2<br />

connections<br />

(ssl-v2-timeout)<br />

and<br />

one<br />

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

SSL<br />

V3<br />

connections<br />

(ssl-v3-timeout).<br />

The<br />

default<br />

SSL<br />

V2<br />

session<br />

timeout<br />

(in<br />

seconds)<br />

is<br />

100<br />

(with<br />

a<br />

possible<br />

range<br />

of<br />

1-100):<br />

[ssl]<br />

ssl-v2-timeout<br />

=<br />

100<br />

The<br />

default<br />

SSL<br />

V3<br />

session<br />

timeout<br />

(in<br />

seconds)<br />

is<br />

7200<br />

(with<br />

a<br />

possible<br />

range<br />

of<br />

1-86400):<br />

[ssl]<br />

ssl-v3-timeout<br />

=<br />

7200<br />

Setting<br />

the<br />

maximum<br />

concurrent<br />

entries<br />

value<br />

The<br />

ssl-max-entries<br />

parameter,<br />

located<br />

in<br />

the<br />

[ssl]<br />

stanza<br />

of<br />

the<br />

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

configuration<br />

file,<br />

sets<br />

the<br />

maximum<br />

number<br />

of<br />

concurrent<br />

entries<br />

in<br />

the<br />

GSKit<br />

SSL<br />

session<br />

ID<br />

cache.<br />

This<br />

value<br />

corresponds<br />

to<br />

the<br />

number<br />

of<br />

concurrent<br />

login<br />

sessions.<br />

When<br />

the<br />

cache<br />

size<br />

reaches<br />

this<br />

value,<br />

entries<br />

are<br />

removed<br />

from<br />

the<br />

cache<br />

according<br />

to<br />

a<br />

least<br />

recently<br />

used<br />

algorithm<br />

to<br />

allow<br />

new<br />

incoming<br />

logins.<br />

The<br />

default<br />

number<br />

of<br />

concurrent<br />

login<br />

sessions<br />

is<br />

4096:<br />

[ssl]<br />

ssl-max-entries<br />

=<br />

4096<br />

For<br />

per<strong>for</strong>mance<br />

considerations,<br />

see<br />

the<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 />

Per<strong>for</strong>mance<br />

Tuning<br />

Guide.<br />

Configuring<br />

the<br />

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

session/credentials<br />

cache<br />

The<br />

following<br />

sections<br />

describe<br />

configuration<br />

and<br />

use<br />

of<br />

the<br />

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

session/credentials<br />

cache:<br />

v<br />

Setting<br />

the<br />

maximum<br />

concurrent<br />

entries<br />

value<br />

v<br />

Setting<br />

the<br />

cache<br />

entry<br />

lifetime<br />

timeout<br />

value<br />

v<br />

Setting<br />

the<br />

cache<br />

entry<br />

inactivity<br />

timeout<br />

value<br />

v<br />

“Credentials<br />

cache<br />

limitation”<br />

on<br />

page<br />

134<br />

Setting<br />

the<br />

maximum<br />

concurrent<br />

entries<br />

value<br />

The<br />

max-entries<br />

parameter,<br />

located<br />

in<br />

the<br />

[session]<br />

stanza<br />

of<br />

the<br />

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

configuration<br />

file,<br />

sets<br />

the<br />

maximum<br />

number<br />

of<br />

concurrent<br />

entries<br />

in<br />

the<br />

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

session/credentials<br />

cache.<br />

Chapter<br />

6.<br />

Authentication<br />

133

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

Saved successfully!

Ooh no, something went wrong!