Authentication methods

The Oracle Empirica Signal software requires users to authenticate by logging in with a unique user name and password.

You can use the following authentication methods:

• Local—User information stored in Oracle Empirica Signal is used for authentication. This method should only be used for internal administration, configuration, and testing, and is not recommended for end users in a production environment.
• Single Sign-On (SSO)—User information stored in a single sign-on application is used for authentication. For example, you might use Oracle Life Sciences Identity and Access Management Service or Oracle Access Manager for single sign-on.
• LDAP—User information stored in a Lightweight Directory Access Protocol (LDAP) directory is used for authentication.

With local and LDAP authentication, Oracle Empirica Signal captures successful and failed login attempts in the User Activity Audit Trail. For more information, see Auditing.

In addition, when a locally authenticated user exceeds the allowable number of login attempts that you set in your password requirements, Oracle Empirica Signal sends an account lockout email notification to the site administrator.

Note:

Local authentication is available for administration and configuration purposes, but it should not be used in production. Oracle recommends using SSO via centralized identity management (for example, IAMS or IDCS) for production environments.

For more information on configuring and implementing authentication methods, see Ways to administer users in the Oracle Empirica Signal User Guide and Online Help.

Authentication is involved in:

• Password requirements
  The Oracle Empirica Signal software provides password options that you can select to establish a password policy for the user accounts for your local users.
• Disabling user accounts
  When an employee leaves your organization, the Oracle Empirica Signal software allows you to disable the employee’s user account to prevent unauthorized system access.