IBM Tivoli Access Manager for e-business: WebSEAL Administration ...

The
entry
level
=
unauthenticated
must
always
be
the
first
in
the
list.
Additional
entries
can
be
placed
in
any
order.
For
example,
to
enable
authentication
strength
levels
for
certificate
authentication
at
the
highest
level,
the
completed
stanza
entry
would
be:
[authentication-levels]
level
=
unauthenticated
level
=
password
level
=
certificate
Note:
There
should
be
only
one
entry
for
each
authentication
mechanism.
2.
Verify
that
each
authentication
method
listed
in
[authentication-levels]
is
enabled.
To
determine
if
an
authentication
method
is
enabled,
check
the
appropriate
entries
in
the
WebSEAL
configuration
file.
To
review
the
necessary
entries
and
access
the
authentication
configuration
instructions,
see
the
following
sections:
v
“Enabling
and
disabling
basic
authentication”
on
page
145
v
“Enabling
and
disabling
forms
authentication”
on
page
147
v
“Enable
token
authentication”
on
page
163.
v
“Enable
certificate
authentication”
on
page
151
Note:
Basic
authentication
is
enabled
by
default.
Specify
the
authentication
strength
login
form
When
a
client
attempts
to
access
a
protected
resource,
and
is
required
to
reauthenticate
to
a
higher
authentication
strength
level,
WebSEAL
presents
a
special
HTML
form.
The
client
uses
the
form
to
supply
the
information
needed
for
the
type
of
authentication
required.
WebSEAL
supplies
a
default
form.
Administrators
can
either
use
the
default
form
or
customize
it
to
fit
the
local
WebSEAL
deployment.
The
location
of
the
default
form
is
specified
in
the
WebSEAL
configuration
file:
[acnt-mgt]
stepup-login
=
stepuplogin.html
Complete
the
following
steps:
1.
Specify
the
name
of
the
authentication
strength
login
form.
To
use
the
default
location
for
the
form,
verify
that
the
WebSEAL
configuration
file
entry
for
stepup-login
contains
the
default
value,
stepuplogin.html.
2.
Optionally,
customize
the
contents
of
the
authentication
strength
login
form.
This
file
contains
macros,
in
the
form
of
%TEXT%
sequences,
which
are
replaced
with
the
appropriate
values.
This
substitution
occurs
within
WebSEAL’s
template
file
processing
functions
and
allows
the
form
to
be
used
for
the
supported
authentication
methods
with
correct
formatting.
It
also
allows
other
information,
such
as
error
message
and
authentication
method
name,
to
be
supplied
in
the
form
for
the
user.
For
more
information
on
using
macros,
see
“Macro
support
for
account
management
pages”
on
page
89.
The
configuration
of
authentication
strength
levels
is
now
complete.
120
IBM
Tivoli
Access
Manager
for
e-business:
WebSEAL
Administration
Guide