Skip Headers
Oracle® Adaptive Access Manager Administrator's Guide
Release 10g (10.1.4.5)

Part Number E12055-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

E Authentication Statuses

The authentication statuses come from bharosa_app.properties and they are configurable.

auth.status.enum.success.name=Success

The user is successfully authenticated.

auth.status.enum.invalid_user.name=Invalid user

The username was invalid and not available in the system.

auth.status.enum.wrong_password.name=Wrong password

The user entered the wrong password. The username was entered correctly, but the password was incorrect.

auth.status.enum.wrong_pin.name=Wrong pin

If user has pin as password and it was entered incorrectly.

auth.status.enum.session_expired.name=Session expired

The user logged in to the application then left it inactive for a length of time. When the user tries to use the application again, a message appears telling him the session has expired. The user will have to log in again.

auth.status.enum.session_reused.name=Session reused

When the session had expired and the user logged in successfully, the status changes from session expired to session reused.

auth.status.enum.user_disabled.name=User disabled

The user was available in the system, but had been disabled in the system for a variety of reasons. The username is valid, but he has been disabled.

auth.status.enum.pending_activation.name=Pending activation

The user has not completed the registration yet.

auth.status.enum.wrong_answer.name=Wrong Answer

The user entered the wrong answer to a challenge question.

auth.status.enum.db_error.name=Database Error

When user was performing a database operation, he encountered an error.

auth.status.enum.system_error.name=System Error

When user was using the application, he encountered an error.

auth.status.enum.block.name=Blocked

If a user is "Blocked," it is because a Model has found certain conditions to be "true" and is set up to respond to these conditions with a "Block Action." If those conditions change, the user may no longer be "Blocked." The "Blocked" status is not necessarily permanent and therefore may or may not require an administrator action to resolve. For example, if the user was blocked because he was logging in from a blocked country, but he is no longer in that country, he may no longer be "Blocked."

auth.status.enum.challenge_block.name=Locked

"Locked" is the status that Oracle Adaptive Access Manager sets if the user fails a question challenge. The "Locked" status is only used if the One-Time-Password (OTP) facility is in use. OTP sends a one-time password to the user via e-mail or SMS text message. If the user exceeds the number of retries when attempting to put in his OTP code, then his account becomes "Locked." After that, a Customer Service Representative must reset the status to "Unlocked" before the account can be used to enter the system.

auth.status.enum.pending.name=Pending

The user has logged into the application, completed registration, but the he did not go through the entire flow.