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.

Step<br />

3<br />

—<br />

Specify<br />

the<br />

attributes<br />

to<br />

be<br />

added<br />

to<br />

the<br />

credential<br />

The<br />

attributes<br />

to<br />

be<br />

added<br />

to<br />

the<br />

credential<br />

are<br />

configured<br />

in<br />

several<br />

stanzas.<br />

Add<br />

this<br />

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

to<br />

the<br />

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

configuration<br />

file.<br />

Note:<br />

Alternatively,<br />

you<br />

can<br />

define<br />

the<br />

attributes<br />

in<br />

a<br />

separate<br />

file,<br />

to<br />

be<br />

called<br />

by<br />

the<br />

entitlement<br />

service.<br />

For<br />

more<br />

in<strong>for</strong>mation,<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 />

Authorization<br />

C<br />

API<br />

Developer<br />

Reference.<br />

Review<br />

the<br />

following<br />

example<br />

entry.<br />

[TAM_CRED_ATTRS_SVC]<br />

eperson<br />

=<br />

azn_cred_registry_id<br />

group<br />

=<br />

cn=enterprise,<br />

o=tivoli<br />

[TAM_CRED_ATTRS_SVC:eperson]<br />

tagvalue_credattrs_lastname<br />

=<br />

sn<br />

tagvalue_credattrs_employeetype<br />

=<br />

employeetype<br />

tagvalue_credattrs_address<br />

=<br />

homepostaladdress<br />

tagvalue_credattrs_email<br />

=<br />

mail<br />

[TAM_CRED_ATTRS_SVC:group]<br />

tagvalue_credattrs_<strong>business</strong>category<br />

=<br />

<strong>business</strong>category<br />

The<br />

stanza<br />

name<br />

[TAM_CRED_ATTRS_SVC]<br />

is<br />

the<br />

Service<br />

ID.<br />

Inside<br />

this<br />

stanza<br />

are<br />

sources<br />

of<br />

attributes<br />

to<br />

be<br />

retrieved.<br />

The<br />

source<br />

names,<br />

such<br />

as<br />

user<br />

and<br />

group<br />

are<br />

used<br />

to<br />

identify<br />

the<br />

source<br />

location<br />

in<br />

the<br />

registry.<br />

You<br />

need<br />

to<br />

define<br />

these.<br />

The<br />

values<br />

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

these<br />

sources<br />

are<br />

registry<br />

identifiers<br />

that<br />

exist<br />

in<br />

the<br />

registry.<br />

The<br />

values<br />

can<br />

be<br />

existing<br />

credential<br />

attribute<br />

names.<br />

If<br />

this<br />

is<br />

the<br />

case,<br />

the<br />

service<br />

automatically<br />

finds<br />

and<br />

uses<br />

the<br />

respective<br />

values.<br />

Configure<br />

the<br />

registry<br />

attributes<br />

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

each<br />

of<br />

the<br />

sources<br />

under<br />

the<br />

service<br />

stanza<br />

in<br />

a<br />

separate<br />

stanza.<br />

The<br />

syntax<br />

of<br />

the<br />

separate<br />

stanza<br />

is<br />

the<br />

service<br />

ID<br />

library<br />

name<br />

followed<br />

by<br />

a<br />

colon<br />

(:)<br />

and<br />

then<br />

the<br />

source<br />

name.<br />

This<br />

connection<br />

is<br />

necessary<br />

because<br />

more<br />

than<br />

one<br />

service<br />

can<br />

be<br />

configured<br />

in<br />

the<br />

same<br />

file.<br />

The<br />

configuration<br />

file<br />

entries<br />

contain<br />

mappings<br />

of<br />

user<br />

registry<br />

attributes<br />

to<br />

user-defined<br />

credential<br />

attributes.<br />

For<br />

example,<br />

in<br />

an<br />

LDAP<br />

user<br />

registry,<br />

the<br />

DN<br />

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

a<br />

user<br />

could<br />

be<br />

cn=joeuser,<br />

o=tivoli<br />

For<br />

this<br />

user,<br />

the<br />

LDAP<br />

user<br />

registry<br />

entries<br />

could<br />

be:<br />

sn=Smith<br />

employeetype=bankteller<br />

homepostaladdress="3004<br />

Mission<br />

St<br />

Santa<br />

Cruz<br />

CA<br />

95060"<br />

email=joeuser@bigco.com<br />

For<br />

the<br />

group<br />

cn=enterprise,o=tivoli,<br />

the<br />

LDAP<br />

group<br />

registry<br />

entry<br />

could<br />

be:<br />

<strong>business</strong>category=finance<br />

Using<br />

the<br />

example<br />

configuration<br />

entries<br />

shown<br />

above,<br />

the<br />

attribute<br />

list<br />

returned<br />

would<br />

have<br />

the<br />

following<br />

entries<br />

Attribute<br />

name<br />

Attribute<br />

value<br />

credattrs_lastname<br />

Smith<br />

credattrs_employeetype<br />

bankteller<br />

credattrs_address<br />

3004<br />

Mission<br />

St<br />

Santa<br />

Cruz<br />

CA<br />

95060<br />

Chapter<br />

7.<br />

Advanced<br />

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

authentication<br />

217

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

Saved successfully!

Ooh no, something went wrong!