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.

1.<br />

Enabling<br />

and<br />

disabling<br />

e-community<br />

authentication<br />

The<br />

e-community-sso-auth<br />

parameter,<br />

located<br />

in<br />

the<br />

[e-community-sso]<br />

stanza<br />

of<br />

the<br />

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

configuration<br />

file,<br />

enables<br />

and<br />

disables<br />

the<br />

e-community<br />

authentication<br />

method,<br />

and<br />

processes<br />

single<br />

sign-on<br />

requests<br />

by<br />

communication<br />

type.<br />

v<br />

To<br />

enable<br />

the<br />

e-community<br />

authentication<br />

method,<br />

enter<br />

″http″,<br />

″https″,<br />

or<br />

″both″.<br />

The<br />

values<br />

″http″,<br />

″https″,<br />

and<br />

″both″<br />

specify<br />

the<br />

type<br />

of<br />

communication<br />

used<br />

by<br />

e-community<br />

participants.<br />

v<br />

To<br />

disable<br />

the<br />

e-community<br />

authentication<br />

method,<br />

enter<br />

″none″.<br />

The<br />

value<br />

″none″<br />

disables<br />

e-community<br />

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

that<br />

server.<br />

The<br />

default<br />

setting<br />

is<br />

″none″.<br />

For<br />

example:<br />

[e-community-sso]<br />

e-community-sso-auth<br />

=<br />

https<br />

Note:<br />

You<br />

must<br />

stop<br />

and<br />

restart<br />

the<br />

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

server<br />

in<br />

order<br />

to<br />

activate<br />

changes<br />

to<br />

the<br />

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

configuration<br />

file.<br />

Complete<br />

all<br />

of<br />

the<br />

applicable<br />

configuration<br />

steps<br />

in<br />

this<br />

section<br />

and<br />

then<br />

restart<br />

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

2.<br />

Specifying<br />

an<br />

e-community<br />

name<br />

The<br />

e-community-name<br />

parameter<br />

identifies<br />

the<br />

unifying<br />

name<br />

of<br />

the<br />

e-community<br />

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

all<br />

participating<br />

servers<br />

in<br />

all<br />

participating<br />

domains.<br />

For<br />

example:<br />

[e-community-sso]<br />

e-community-name<br />

=<br />

companyABC<br />

The<br />

e-community-name<br />

value<br />

must<br />

be<br />

the<br />

same<br />

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

all<br />

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

servers<br />

in<br />

all<br />

domains<br />

that<br />

are<br />

participating<br />

in<br />

the<br />

e-community.<br />

3.<br />

Configuring<br />

the<br />

single<br />

sign-on<br />

authentication<br />

mechanism<br />

The<br />

default<br />

e-community<br />

configuration<br />

requires<br />

that<br />

you<br />

enable<br />

the<br />

sso-create<br />

and<br />

sso-consume<br />

single<br />

sign-on<br />

authentication<br />

mechanisms.<br />

The<br />

sso-create<br />

mechanism<br />

is<br />

required<br />

by<br />

the<br />

initial<br />

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

server<br />

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

creating<br />

the<br />

″vouch<br />

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

token<br />

and<br />

building<br />

the<br />

redirected<br />

request.<br />

The<br />

sso-consume<br />

mechanism<br />

is<br />

required<br />

by<br />

the<br />

receiving<br />

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

server<br />

to<br />

decode<br />

the<br />

″vouch<br />

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

token<br />

and<br />

build<br />

the<br />

user<br />

credentials<br />

from<br />

the<br />

identity<br />

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

contained<br />

in<br />

the<br />

token.<br />

For<br />

the<br />

default<br />

e-community<br />

configuration,<br />

each<br />

parameter<br />

specifies<br />

a<br />

built-in<br />

″vouch<br />

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

token<br />

library<br />

file.<br />

One<br />

library<br />

contains<br />

the<br />

code<br />

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

the<br />

token<br />

create<br />

functionality<br />

and<br />

the<br />

other<br />

library<br />

contains<br />

the<br />

code<br />

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

the<br />

token<br />

consume<br />

functionality.<br />

v<br />

On<br />

UNIX,<br />

the<br />

library<br />

files<br />

are<br />

called<br />

libssocreate.<br />

{so<br />

|<br />

a<br />

|<br />

sl}<br />

and<br />

libssoconsume.<br />

{so<br />

|<br />

a<br />

|<br />

sl}.<br />

v<br />

On<br />

Windows,<br />

the<br />

library<br />

files<br />

are<br />

DLL<br />

files<br />

called<br />

ssocreate.dll<br />

and<br />

ssoconsume.dll.<br />

Authentication<br />

Mechanism<br />

Single<br />

Sign-on<br />

Token<br />

Library<br />

Solaris<br />

AIX<br />

Windows<br />

HP-UX<br />

sso-create<br />

libssocreate.so<br />

libssocreate.a<br />

ssocreate.dll<br />

libssocreate.sl<br />

sso-consume<br />

libssoconsume.so<br />

libssoconsume.a<br />

ssoconsume.dll<br />

libssoconsume.sl<br />

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