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.

Table<br />

22.<br />

Authentication<br />

library<br />

types<br />

specified<br />

in<br />

the<br />

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

configuration<br />

file<br />

(continued)<br />

failover-certificate<br />

Library<br />

that<br />

implements<br />

failover<br />

cookie<br />

authentication<br />

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

certificate<br />

authentication.<br />

failover-http-request<br />

Library<br />

that<br />

implements<br />

failover<br />

cookie<br />

authentication<br />

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

HTTP<br />

header<br />

authentication<br />

or<br />

IP<br />

address<br />

authentication.<br />

failover-cdsso<br />

Library<br />

that<br />

implements<br />

failover<br />

cookie<br />

authentication<br />

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

cross-domain<br />

single<br />

sign-on<br />

authentication.<br />

passwd-strength<br />

Library<br />

that<br />

en<strong>for</strong>ces<br />

custom<br />

password<br />

strength<br />

authentication<br />

policies.<br />

cred-ext-attrs<br />

Custom<br />

authentication<br />

module<br />

used<br />

to<br />

supply<br />

extended<br />

attribute<br />

data<br />

to<br />

user<br />

credential<br />

You<br />

use<br />

the<br />

[authentication-mechanisms]<br />

stanza<br />

to<br />

configure<br />

the<br />

authentication<br />

method<br />

and<br />

the<br />

implementation<br />

in<br />

the<br />

following<br />

<strong>for</strong>mat:<br />

authentication_method_entry<br />

=<br />

built-in_shared_library<br />

Authentication<br />

conversion<br />

library<br />

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

provides<br />

an<br />

authentication<br />

conversion<br />

library<br />

that<br />

converts<br />

authentication<br />

data<br />

from<br />

UTF-8<br />

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

to<br />

non-UTF-8<br />

<strong>for</strong>mat.<br />

For<br />

Version<br />

5.1,<br />

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

produces<br />

authentication<br />

data<br />

in<br />

UTF-8<br />

<strong>for</strong>mat.<br />

Prior<br />

to<br />

Version<br />

5.1,<br />

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

produced<br />

authentication<br />

data<br />

in<br />

the<br />

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

of<br />

the<br />

local<br />

code<br />

page.<br />

Thus,<br />

external<br />

authentication<br />

modules,<br />

such<br />

as<br />

CDASs,<br />

that<br />

were<br />

written<br />

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

versions<br />

of<br />

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

prior<br />

to<br />

Version<br />

5.1<br />

might<br />

need<br />

to<br />

use<br />

the<br />

conversion<br />

library.<br />

For<br />

more<br />

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

on<br />

the<br />

conversion<br />

library,<br />

including<br />

configuration<br />

instructions<br />

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

Web<br />

Security<br />

Developer<br />

Reference.<br />

For<br />

more<br />

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

on<br />

<strong>WebSEAL</strong>’s<br />

use<br />

of<br />

UTF-8<br />

encoding,<br />

see<br />

“Multi-locale<br />

support<br />

with<br />

UTF-8”<br />

on<br />

page<br />

44.<br />

Default<br />

configuration<br />

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

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

authentication<br />

By<br />

default,<br />

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

is<br />

set<br />

to<br />

authenticate<br />

clients<br />

over<br />

SSL<br />

using<br />

basic<br />

authentication<br />

(BA)<br />

user<br />

names<br />

and<br />

passwords<br />

(LDAP<br />

registry).<br />

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

is<br />

normally<br />

enabled<br />

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

both<br />

TCP<br />

and<br />

SSL<br />

access.<br />

There<strong>for</strong>e,<br />

a<br />

typical<br />

configuration<br />

of<br />

the<br />

[authentication-mechanisms]<br />

stanza<br />

includes<br />

support<br />

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

username<br />

and<br />

password<br />

(LDAP<br />

registry)<br />

and<br />

support<br />

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

client-side<br />

certificates<br />

over<br />

SSL.<br />

The<br />

following<br />

example<br />

represents<br />

the<br />

typical<br />

configuration<br />

of<br />

the<br />

[authentication-mechanisms]<br />

stanza<br />

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

Solaris:<br />

[authentication-mechanisms]<br />

passwd-ldap<br />

=<br />

libldapauthn.so<br />

cert-ssl<br />

=<br />

libsslauthn.so<br />

To<br />

configure<br />

other<br />

authentication<br />

methods,<br />

add<br />

the<br />

appropriate<br />

parameter<br />

with<br />

its<br />

shared<br />

library<br />

(or<br />

CDAS<br />

module).<br />

Chapter<br />

6.<br />

Authentication<br />

141

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

Saved successfully!

Ooh no, something went wrong!