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.

HTTP_HTTP_header_name<br />

For<br />

example:<br />

HTTP_PD-USER-SESSION-ID=user_session_id<br />

Terminating<br />

user<br />

sessions<br />

A<br />

user<br />

can<br />

initiate<br />

the<br />

termination<br />

of<br />

the<br />

current<br />

session<br />

through<br />

the<br />

pkmslogout<br />

command.<br />

Additionally,<br />

the<br />

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

in<br />

the<br />

User<br />

Session<br />

ID<br />

allows<br />

administrators<br />

and<br />

back-end<br />

applications<br />

to<br />

track<br />

and<br />

manage<br />

users.<br />

This<br />

section<br />

describes<br />

two<br />

methods<br />

of<br />

terminating<br />

the<br />

user<br />

session<br />

at<br />

an<br />

administration<br />

level:<br />

v<br />

“Using<br />

<strong>Administration</strong><br />

API<br />

to<br />

terminate<br />

single<br />

user<br />

sessions”<br />

on<br />

page<br />

345<br />

v<br />

“Using<br />

pdadmin<br />

to<br />

terminate<br />

all<br />

user<br />

sessions”<br />

on<br />

page<br />

345<br />

Using<br />

<strong>Administration</strong><br />

API<br />

to<br />

terminate<br />

single<br />

user<br />

sessions<br />

A<br />

back-end<br />

application<br />

can<br />

use<br />

the<br />

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

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

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

administration<br />

API<br />

to<br />

terminate<br />

a<br />

specific<br />

user<br />

session<br />

based<br />

on<br />

the<br />

User<br />

Session<br />

ID<br />

passed<br />

across<br />

the<br />

junction.<br />

The<br />

application<br />

invokes<br />

the<br />

ivadmin_server_per<strong>for</strong>mtask()<br />

function<br />

inside<br />

its<br />

terminate<br />

code.<br />

The<br />

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

server<br />

instance<br />

and<br />

the<br />

User<br />

Session<br />

ID<br />

are<br />

included<br />

as<br />

parameters<br />

to<br />

this<br />

function.<br />

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

verifies<br />

that<br />

the<br />

back-end<br />

server<br />

initiating<br />

the<br />

terminate<br />

operation<br />

has<br />

appropriate<br />

permissions<br />

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

terminating<br />

the<br />

user<br />

session.<br />

It<br />

is<br />

important<br />

to<br />

consider<br />

the<br />

conditions<br />

under<br />

which<br />

this<br />

command<br />

might<br />

be<br />

used.<br />

If<br />

the<br />

intent<br />

is<br />

to<br />

make<br />

sure<br />

a<br />

user<br />

is<br />

removed<br />

from<br />

the<br />

secure<br />

domain<br />

entirely,<br />

the<br />

termination<br />

of<br />

a<br />

single<br />

user<br />

is<br />

only<br />

effective<br />

when,<br />

in<br />

addition,<br />

the<br />

account<br />

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

that<br />

user<br />

is<br />

made<br />

invalid<br />

(removed).<br />

Certain<br />

authentication<br />

methods—such<br />

as<br />

Basic<br />

Authentication,<br />

client-side<br />

certificate,<br />

and<br />

failover<br />

cookies—return<br />

cached<br />

authentication<br />

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

automatically<br />

with<br />

no<br />

user<br />

intervention.<br />

The<br />

termination<br />

action<br />

would<br />

not<br />

prevent<br />

return<br />

logins<br />

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

a<br />

user<br />

using<br />

any<br />

of<br />

those<br />

authentication<br />

methods.<br />

You<br />

must<br />

additionally<br />

invalidate<br />

the<br />

appropriate<br />

user<br />

account<br />

in<br />

the<br />

registry.<br />

Refer<br />

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

<strong>Administration</strong><br />

C<br />

API<br />

Developer<br />

Reference<br />

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

further<br />

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

Using<br />

pdadmin<br />

to<br />

terminate<br />

all<br />

user<br />

sessions<br />

An<br />

administrator<br />

can<br />

use<br />

the<br />

pdadmin<br />

utility<br />

to<br />

terminate<br />

all<br />

sessions<br />

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

a<br />

specified<br />

user<br />

based<br />

on<br />

the<br />

user<br />

ID.<br />

pdadmin><br />

server<br />

task<br />

instance_name-webseald-host_name<br />

terminate<br />

all_sessions<br />

user_id<br />

The<br />

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

credentials<br />

cache<br />

is<br />

organized<br />

to<br />

cross-reference<br />

user<br />

ID,<br />

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

session<br />

ID,<br />

and<br />

cache<br />

entry<br />

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

A<br />

user<br />

always<br />

has<br />

the<br />

same<br />

user<br />

ID<br />

across<br />

multiple<br />

sessions.<br />

Each<br />

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

session<br />

ID,<br />

however,<br />

is<br />

unique.<br />

The<br />

terminate<br />

all_sessions<br />

command<br />

removes<br />

all<br />

cache<br />

entries<br />

belonging<br />

to<br />

the<br />

user_id.<br />

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

checks<br />

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

appropriate<br />

permissions<br />

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

the<br />

administrator<br />

initiating<br />

the<br />

command<br />

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

terminating<br />

user<br />

sessions.<br />

It<br />

is<br />

important<br />

to<br />

consider<br />

the<br />

conditions<br />

under<br />

which<br />

this<br />

command<br />

might<br />

be<br />

used.<br />

If<br />

the<br />

intent<br />

is<br />

to<br />

make<br />

sure<br />

a<br />

certain<br />

group<br />

of<br />

users<br />

are<br />

removed<br />

from<br />

the<br />

secure<br />

domain<br />

entirely,<br />

the<br />

terminate<br />

all_sessions<br />

command<br />

is<br />

only<br />

effective<br />

when,<br />

in<br />

addition,<br />

the<br />

accounts<br />

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

those<br />

users<br />

are<br />

made<br />

invalid<br />

(removed).<br />

Certain<br />

authentication<br />

methods—such<br />

as<br />

Basic<br />

Authentication,<br />

client-side<br />

certificate,<br />

and<br />

failover<br />

cookies—return<br />

cached<br />

authentication<br />

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

Chapter<br />

12.<br />

Application<br />

integration<br />

345

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

Saved successfully!

Ooh no, something went wrong!