Authentication methods
The 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 Empirica Signal is used for authentication.
- Single Sign-On (SSO)—User information stored in a single sign-on application is used for authentication. For example, you might use Oracle Health Sciences Identity and Access Management Services 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, 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, Empirica Signal sends an account lockout email notification to the site administrator.
For more information on configuring and implementing authentication methods, see the Empirica Signal User Guide.