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.

Credential<br />

refresh<br />

configuration<br />

To<br />

configure<br />

credential<br />

refresh,<br />

complete<br />

the<br />

following<br />

steps:<br />

v<br />

“Step<br />

1:<br />

Specify<br />

attributes<br />

to<br />

preserve<br />

or<br />

refresh”<br />

v<br />

“Step<br />

2:<br />

Enable<br />

user<br />

session<br />

IDs”<br />

v<br />

“Step<br />

3:<br />

Enable<br />

placement<br />

of<br />

server<br />

name<br />

into<br />

junction<br />

header”<br />

Step<br />

1:<br />

Specify<br />

attributes<br />

to<br />

preserve<br />

or<br />

refresh<br />

1.<br />

Stop<br />

the<br />

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

server.<br />

2.<br />

Edit<br />

the<br />

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

configuration<br />

file.<br />

v<br />

Add<br />

entries<br />

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

attributes<br />

to<br />

preserve.<br />

For<br />

example:<br />

[credential-refresh-attributes]<br />

my_cred_attribute1<br />

=<br />

preserve<br />

my_cred_attribute2<br />

=<br />

preserve<br />

v<br />

Add<br />

entries<br />

to<br />

refresh:<br />

[credential-refresh-attributes]<br />

my_cred_attribute3<br />

=<br />

refresh<br />

my_cred_attribute4<br />

=<br />

refresh<br />

v<br />

When<br />

appropriate<br />

use<br />

the<br />

order<br />

of<br />

the<br />

entries<br />

to<br />

handle<br />

both<br />

specific<br />

entries<br />

and<br />

groups<br />

of<br />

entries.<br />

For<br />

example,<br />

to<br />

preserve<br />

the<br />

attribute<br />

special_cred_attr1,<br />

but<br />

refresh<br />

all<br />

other<br />

attributes<br />

with<br />

the<br />

naming<br />

construct<br />

of<br />

special_cred_attr*,<br />

add<br />

the<br />

following<br />

entries:<br />

[credential-refresh-attributes]<br />

special_cred_attr1<br />

=<br />

preserve<br />

special_cred_attr*<br />

=<br />

refresh<br />

Step<br />

2:<br />

Enable<br />

user<br />

session<br />

IDs<br />

Ensure<br />

that<br />

user<br />

session<br />

IDs<br />

are<br />

enabled<br />

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

the<br />

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

server<br />

instance.<br />

The<br />

credential<br />

refresh<br />

administration<br />

command<br />

does<br />

not<br />

work<br />

when<br />

user<br />

session<br />

IDs<br />

are<br />

not<br />

enabled.<br />

[session]<br />

user-session-ids<br />

=<br />

yes<br />

Step<br />

3:<br />

Enable<br />

placement<br />

of<br />

server<br />

name<br />

into<br />

junction<br />

header<br />

A<br />

header<br />

with<br />

the<br />

URI-encoded<br />

authorization<br />

API<br />

administration<br />

server<br />

name<br />

is<br />

passed<br />

to<br />

all<br />

junction<br />

servers.<br />

When<br />

no<br />

header<br />

name<br />

is<br />

specified,<br />

the<br />

header<br />

will<br />

not<br />

be<br />

sent<br />

to<br />

the<br />

junction.<br />

The<br />

value<br />

is<br />

set<br />

in<br />

the<br />

default<br />

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

configuration<br />

file.<br />

[header-names]<br />

server-name<br />

=<br />

iv_server_name<br />

This<br />

setting<br />

controls<br />

the<br />

name<br />

of<br />

the<br />

header<br />

used<br />

to<br />

pass<br />

the<br />

name<br />

of<br />

the<br />

server<br />

to<br />

junctioned<br />

applications.<br />

For<br />

example,<br />

when<br />

server-name<br />

=<br />

iv_server_name,<br />

and<br />

the<br />

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

server<br />

instance<br />

is<br />

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

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

passes<br />

the<br />

following<br />

header<br />

to<br />

the<br />

junction:<br />

iv-server-name:default-webseald-diamond.subnet1.ibm.com<br />

Typically,<br />

the<br />

default<br />

value<br />

iv_server_name<br />

is<br />

used.<br />

However,<br />

you<br />

can<br />

replace<br />

it<br />

with<br />

any<br />

valid<br />

string.<br />

Valid<br />

strings<br />

are<br />

limited<br />

to<br />

the<br />

following<br />

characters:<br />

[A-Z],<br />

[a-z],<br />

[0–9],<br />

hyphen<br />

(<br />

-<br />

),<br />

or<br />

underscore<br />

(<br />

_<br />

).<br />

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

accepts<br />

a<br />

blank<br />

value<br />

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

server-name.<br />

This<br />

is<br />

not<br />

usually<br />

useful,<br />

but<br />

could<br />

be<br />

applicable<br />

if<br />

the<br />

junctioned<br />

application<br />

chooses<br />

to<br />

have<br />

the<br />

server<br />

name<br />

hardcoded<br />

instead<br />

of<br />

obtaining<br />

it<br />

from<br />

the<br />

header.<br />

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