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.

v<br />

Require<br />

a<br />

specific<br />

authentication<br />

strength<br />

level<br />

when<br />

the<br />

IP<br />

address<br />

of<br />

the<br />

requesting<br />

client<br />

is<br />

within<br />

a<br />

defined<br />

range<br />

of<br />

IP<br />

addresses.<br />

Syntax:<br />

pdadmin><br />

pop<br />

modify<br />

pop_name<br />

set<br />

ipauth<br />

add<br />

network<br />

netmask<br />

level_index<br />

Note<br />

that<br />

the<br />

pdadmin<br />

pop<br />

modify<br />

set<br />

ipauth<br />

add<br />

command<br />

specifies<br />

both<br />

the<br />

network<br />

addresses<br />

and<br />

the<br />

required<br />

authentication<br />

level<br />

in<br />

the<br />

IP<br />

Endpoint<br />

Authentication<br />

Method<br />

attribute.<br />

For<br />

example,<br />

to<br />

require<br />

users<br />

from<br />

IP<br />

address<br />

range<br />

9.1.2.[0–255]<br />

to<br />

use<br />

authentication<br />

strength<br />

level<br />

1:<br />

pdadmin><br />

pop<br />

modify<br />

test<br />

set<br />

ipauth<br />

add<br />

9.1.2.1<br />

255.255.255.0<br />

1<br />

Note<br />

that<br />

the<br />

value<br />

specified<br />

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

the<br />

netmask<br />

determines<br />

the<br />

range<br />

of<br />

network<br />

addresses<br />

affected.<br />

The<br />

number<br />

0<br />

in<br />

the<br />

netmask<br />

serves<br />

as<br />

a<br />

wildcard<br />

to<br />

mean<br />

all<br />

IP<br />

addresses<br />

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

that<br />

subnet.<br />

See<br />

the<br />

example<br />

that<br />

follows.<br />

Table<br />

21.<br />

Using<br />

netmask<br />

to<br />

specify<br />

a<br />

network<br />

range<br />

Example<br />

usage<br />

IP<br />

Address<br />

Netmask<br />

Network<br />

range<br />

affected<br />

9.1.2.3<br />

255.255.255.0<br />

9.1.2.[0–255]<br />

9.1.2.3<br />

255.255.0.0<br />

9.1.[0–255].[0–255]<br />

9.1.2.3<br />

255.0.0.0<br />

9.[0–255].[0–255].[0–255]<br />

v<br />

Require<br />

requests<br />

from<br />

one<br />

specific<br />

IP<br />

address<br />

to<br />

use<br />

a<br />

specified<br />

authentication<br />

strength<br />

level.<br />

For<br />

example,<br />

to<br />

require<br />

requests<br />

from<br />

IP<br />

address<br />

9.1.2.3<br />

to<br />

use<br />

authentication<br />

strength<br />

level<br />

1:<br />

pdadmin><br />

pop<br />

modify<br />

test<br />

set<br />

ipauth<br />

add<br />

9.1.2.3<br />

255.255.255.255<br />

1<br />

To<br />

require<br />

requests<br />

from<br />

all<br />

IP<br />

addresses<br />

on<br />

subnet<br />

9.1.2.x<br />

to<br />

use<br />

authentication<br />

strength<br />

level<br />

1:<br />

pdadmin><br />

pop<br />

modify<br />

test<br />

set<br />

ipauth<br />

add<br />

9.1.2.3<br />

255.255.255.0<br />

1<br />

v<br />

Disable<br />

use<br />

of<br />

authentication<br />

strength<br />

level<br />

step-up<br />

by<br />

all<br />

requests<br />

from<br />

a<br />

range<br />

of<br />

network<br />

addresses.<br />

The<br />

syntax<br />

is:<br />

pdadmin><br />

pop<br />

modify<br />

pop_name<br />

set<br />

ipauth<br />

remove<br />

network<br />

netmask<br />

For<br />

example,<br />

to<br />

disable<br />

all<br />

requests<br />

from<br />

the<br />

range<br />

of<br />

IP<br />

addresses<br />

on<br />

the<br />

9.1.2.x<br />

subnet:<br />

pdadmin><br />

pop<br />

modify<br />

test<br />

set<br />

ipauth<br />

remove<br />

9.1.2.1<br />

255.255.255.0<br />

v<br />

Allow<br />

access<br />

to<br />

the<br />

protected<br />

resource<br />

based<br />

solely<br />

on<br />

IP<br />

address,<br />

or<br />

range<br />

of<br />

IP<br />

addresses,<br />

regardless<br />

of<br />

the<br />

authentication<br />

strength<br />

level.<br />

This<br />

restriction<br />

is<br />

en<strong>for</strong>ced<br />

by<br />

specifying<br />

the<br />

IP<br />

address<br />

or<br />

addresses,<br />

and<br />

assigning<br />

an<br />

authentication<br />

level<br />

of<br />

zero<br />

(0).<br />

For<br />

example,<br />

to<br />

allow<br />

requests<br />

from<br />

IP<br />

address<br />

9.1.2.3,<br />

regardless<br />

of<br />

authentication<br />

strength<br />

level:<br />

pdadmin><br />

pop<br />

modify<br />

test<br />

set<br />

ipauth<br />

add<br />

9.1.2.3<br />

255.255.255.255<br />

0<br />

Likewise,<br />

to<br />

allow<br />

requests<br />

from<br />

all<br />

IP<br />

addresses<br />

on<br />

the<br />

9.1.2.x<br />

subnet,<br />

regardless<br />

of<br />

authentication<br />

strength<br />

level:<br />

Chapter<br />

5.<br />

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

security<br />

policy<br />

123

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

Saved successfully!

Ooh no, something went wrong!