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.

1.<br />

Ensure<br />

that<br />

the<br />

server-name<br />

key<br />

is<br />

set<br />

in<br />

the<br />

configuration<br />

file<br />

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

the<br />

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

server<br />

instance.<br />

2.<br />

Restart<br />

the<br />

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

server.<br />

Credential<br />

refresh<br />

usage<br />

Topic<br />

index:<br />

v<br />

“Refresh<br />

credentials<br />

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

a<br />

specified<br />

user”<br />

v<br />

“Troubleshooting”<br />

Refresh<br />

credentials<br />

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

a<br />

specified<br />

user<br />

Send<br />

a<br />

command<br />

to<br />

the<br />

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

server,<br />

instructing<br />

it<br />

to<br />

per<strong>for</strong>m<br />

a<br />

credential<br />

refresh<br />

operation<br />

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

all<br />

of<br />

the<br />

sessions<br />

of<br />

the<br />

specified<br />

user<br />

on<br />

the<br />

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

server.<br />

The<br />

syntax<br />

is:<br />

pdadmin><br />

server<br />

task<br />

instance_name-webseald-host_name<br />

\<br />

refresh<br />

all_sessions<br />

user_name<br />

Enter<br />

the<br />

above<br />

command<br />

as<br />

one<br />

continuous<br />

command<br />

line.<br />

To<br />

obtain<br />

the<br />

server<br />

name<br />

in<br />

the<br />

correct<br />

<strong>for</strong>mat,<br />

use<br />

the<br />

pdadmin<br />

server<br />

list<br />

command.<br />

Then<br />

enter<br />

the<br />

pdadmin<br />

command<br />

to<br />

refresh<br />

all<br />

sessions.<br />

For<br />

example,<br />

when<br />

logged<br />

in<br />

to<br />

pdadmin<br />

as<br />

the<br />

administrative<br />

user<br />

sec_master:<br />

pdadmin<br />

sec_master><br />

server<br />

list<br />

default-webseald-diamond.subnet1.ibm.com<br />

default-webseald-cmd<br />

pdadmin<br />

sec_master><br />

server<br />

task<br />

default-webseald-diamond.subnet1.ibm.com<br />

\<br />

refresh<br />

all_sessions<br />

brian<br />

DPWWA2043I<br />

The<br />

user’s<br />

credential<br />

was<br />

updated.<br />

Note<br />

that<br />

the<br />

pdadmin<br />

server<br />

task<br />

command<br />

must<br />

each<br />

be<br />

entered<br />

as<br />

one<br />

continuous<br />

command<br />

line<br />

A<br />

warning<br />

message<br />

is<br />

returned<br />

if<br />

the<br />

user<br />

is<br />

not<br />

logged<br />

in<br />

to<br />

the<br />

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

server.<br />

Usage<br />

notes:<br />

v<br />

Configure<br />

credential<br />

refresh<br />

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

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

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

using<br />

this<br />

pdadmin<br />

command.<br />

See<br />

“Credential<br />

refresh<br />

configuration”<br />

on<br />

page<br />

224.<br />

v<br />

You<br />

must<br />

issue<br />

a<br />

separate<br />

pdadmin<br />

command<br />

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

each<br />

user<br />

whose<br />

credentials<br />

are<br />

to<br />

be<br />

refreshed.<br />

You<br />

cannot<br />

refresh<br />

credentials<br />

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

more<br />

than<br />

one<br />

user<br />

at<br />

a<br />

time.<br />

v<br />

The<br />

user<br />

invoking<br />

this<br />

command<br />

must<br />

have<br />

server<br />

admin<br />

(The<br />

s<br />

ACL<br />

bit)<br />

permission<br />

on<br />

the<br />

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

server<br />

object.<br />

This<br />

prevents<br />

unauthorized<br />

users<br />

from<br />

per<strong>for</strong>ming<br />

credential<br />

refresh<br />

operations.<br />

Note<br />

that<br />

the<br />

name<br />

of<br />

the<br />

hostname_instance_name<br />

server<br />

object<br />

is<br />

different<br />

than<br />

the<br />

server<br />

name.<br />

To<br />

determine<br />

the<br />

exact<br />

name<br />

of<br />

the<br />

server<br />

object,<br />

use<br />

pdadmin<br />

object<br />

list.<br />

For<br />

example,<br />

when<br />

logged<br />

in<br />

to<br />

pdadmin<br />

as<br />

the<br />

administrative<br />

user<br />

sec_master:<br />

pdadmin<br />

sec_master><br />

object<br />

list<br />

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

/<strong>WebSEAL</strong>/cmd-default<br />

/<strong>WebSEAL</strong>/diamond.subnet1.ibm.com-default<br />

Troubleshooting<br />

v<br />

Problem:<br />

When<br />

a<br />

new<br />

group<br />

entry<br />

is<br />

added<br />

to<br />

a<br />

user’s<br />

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

in<br />

a<br />

user<br />

registry,<br />

a<br />

credential<br />

refresh<br />

command<br />

does<br />

not<br />

obtain<br />

the<br />

new<br />

entry.<br />

Solution:<br />

Some<br />

user<br />

registries<br />

maintain<br />

cached<br />

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

The<br />

cache<br />

is<br />

updated<br />

periodically.<br />

The<br />

cache<br />

update<br />

must<br />

take<br />

place<br />

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

the<br />

credential<br />

Chapter<br />

7.<br />

Advanced<br />

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

authentication<br />

225

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

Saved successfully!

Ooh no, something went wrong!