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.

Port<br />

on<br />

which<br />

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

listens<br />

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

HTTPS<br />

requests.<br />

This<br />

value<br />

is<br />

set<br />

during<br />

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

configuration.<br />

When<br />

the<br />

default<br />

HTTP<br />

port<br />

is<br />

already<br />

in<br />

use,<br />

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

configuration<br />

suggests<br />

the<br />

next<br />

available<br />

(unused)<br />

port<br />

number.<br />

The<br />

administrator<br />

can<br />

modify<br />

this<br />

number.<br />

Valid<br />

values<br />

include<br />

any<br />

port<br />

number<br />

not<br />

already<br />

in<br />

use<br />

on<br />

the<br />

host.<br />

This<br />

stanza<br />

entry<br />

is<br />

required.<br />

Default<br />

value:<br />

80<br />

Example:<br />

http-port<br />

=<br />

80<br />

max-client-read<br />

=<br />

number_of_bytes<br />

Specifies<br />

the<br />

maximum<br />

number<br />

of<br />

bytes<br />

that<br />

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

will<br />

hold<br />

in<br />

internal<br />

buffers<br />

while<br />

reading<br />

from<br />

a<br />

client.<br />

Affects<br />

the<br />

maximum<br />

size<br />

of<br />

URLs,<br />

HTTP<br />

Headers,<br />

and<br />

the<br />

size<br />

of<br />

a<br />

request<br />

that<br />

will<br />

be<br />

cached.<br />

Must<br />

be<br />

set<br />

to<br />

at<br />

least<br />

twice<br />

the<br />

value<br />

of<br />

request-body-max-read.<br />

Minimum<br />

number<br />

of<br />

bytes:<br />

32678.<br />

If<br />

the<br />

value<br />

is<br />

set<br />

to<br />

a<br />

number<br />

below<br />

32768,<br />

the<br />

value<br />

is<br />

ignored<br />

and<br />

a<br />

value<br />

of<br />

32768<br />

is<br />

used.<br />

There<br />

is<br />

no<br />

maximum.<br />

This<br />

stanza<br />

entry<br />

is<br />

required.<br />

Default<br />

value:<br />

32768<br />

Example:<br />

max-client-read<br />

=<br />

32768<br />

request-body-max-read<br />

=<br />

number_of_bytes<br />

Maximum<br />

number<br />

of<br />

bytes<br />

to<br />

read<br />

in<br />

as<br />

content<br />

from<br />

the<br />

body<br />

of<br />

POST<br />

requests.<br />

Used<br />

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

dynurl,<br />

authentication,<br />

and<br />

request<br />

caching.<br />

Minimum<br />

number<br />

of<br />

bytes:<br />

512.<br />

Maximum<br />

number<br />

of<br />

bytes:<br />

32768.<br />

However,<br />

the<br />

maximum<br />

can<br />

be<br />

increased<br />

by<br />

raising<br />

the<br />

value<br />

of<br />

max-client-read.<br />

See<br />

“Configuring<br />

server-side<br />

caching<br />

parameters”<br />

on<br />

page<br />

201.<br />

This<br />

stanza<br />

entry<br />

is<br />

required.<br />

Default<br />

value:<br />

4096<br />

Example:<br />

request-body-max-read<br />

=<br />

4096<br />

request-max-cache<br />

=<br />

number_of_bytes<br />

Maximum<br />

amount<br />

of<br />

data<br />

to<br />

cache.<br />

This<br />

is<br />

used<br />

to<br />

cache<br />

request<br />

data<br />

when<br />

a<br />

user<br />

is<br />

prompted<br />

to<br />

authenticate<br />

be<strong>for</strong>e<br />

a<br />

request<br />

can<br />

be<br />

fulfilled.<br />

This<br />

value<br />

should<br />

be<br />

a<br />

positive<br />

integer.<br />

If<br />

set<br />

to<br />

zero<br />

(0),<br />

the<br />

user<br />

login<br />

succeeds<br />

but<br />

the<br />

request<br />

fails<br />

because<br />

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

cannot<br />

cache<br />

the<br />

request<br />

data.<br />

There<br />

is<br />

no<br />

maximum<br />

value.<br />

This<br />

stanza<br />

entry<br />

is<br />

required.<br />

Default<br />

value:<br />

8192<br />

Example:<br />

request-max-cache<br />

=<br />

8192<br />

See<br />

also<br />

“Configuring<br />

server-side<br />

caching<br />

parameters”<br />

on<br />

page<br />

201.<br />

dynurl-map<br />

=<br />

relative_pathname<br />

Appendix<br />

A.<br />

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

configuration<br />

file<br />

reference<br />

387

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

Saved successfully!

Ooh no, something went wrong!