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

Table
18.
Authentication
errors
(continued)
Account
lock-out
13212132
320938290
Account
lock-out:
user
Expired
password
132120cc
320938188
The
user’s
password
has
expired.
General
failure
All
others
All
others
user
To
determine
the
reason
for
an
audited
event
such
as
an
account
lock-out
(due,
for
example,
to
a
three
strikes
policy),
obtain
the
error
code
as
shown
in
the
table
above.
The
error
code
is
contained
in
the
audit
output
in
the
tag:
"13212132">0
Invoke
the
pdadmin
errtext
command
for
the
error
code
to
receive
a
reason
for
the
outcome.
For
example:
>
pdadmin
errtext
13212132
This
account
has
been
temporarily
locked
out
due
to
too
many
failed
login
attempts
Error
codes
for
Tivoli
Access
Manager
are
described
in
the
IBM
Tivoli
Access
Manager
Error
Message
Reference.
Audit
data
in
UTF-8
format
WebSEAL
produces
audit
data
using
UTF-8
encoding.
When
the
operating
system
uses
a
non-UTF-8
local
code
page,
WebSEAL
automatically
converts
audit
data
to
a
data
format
to
match
the
non-UTF-8
local
code
page.
In
some
cases,
the
conversion
from
UTF-8
to
non-UTF-8
encoding
can
result
in
data
loss.
For
this
reason,
it
is
recommended
that
the
WebSEAL
process
run
in
a
locale
environment
that
uses
UTF-8
encoded
code
pages.
It
is
possible
to
obtain
UTF-8
logs
when
running
in
a
non-UTF-8
locale.
Use
the
UTF8FILE
type
in
the
routing
file.
Note
that
when
data
loss
occurs,
the
audit
file
entry
contains
a
series
of
question
marks
(????)
at
the
location
where
data
conversion
was
problematic.
For
more
information,
see
“Multi-locale
support
with
UTF-8”
on
page
44.
104
IBM
Tivoli
Access
Manager
for
e-business:
WebSEAL
Administration
Guide