Configure single sign-on in a self-hosted environment

Adding Oracle Empirica Signal to a single sign-on (SSO) self-hosted environment requires you to perform configuration tasks outside of the application before you enable SSO for Oracle Empirica Signal users. Your application environment determines the configuration responsibilities:

Single Sign-On configuration checklist

#	Task	Responsibility	Source for Instructions
1	Install and configure an SSO application such as Oracle Access Manager	Customer	Contact Oracle for assistance.
2	Configure a WebGate agent on the SSO server.	Oracle	Contact Oracle for assistance.
3	Install and configure WebGate on the Oracle Empirica Signal application server.	Oracle	Contact Oracle for assistance.
4	Uncomment single sign-on properties in the webvdme.properties file.	Customer	Oracle Health Sciences Empirica Signal Installation Guide.
5	Specify the URL for a custom logout page (optional).	Customer	Oracle Health Sciences Empirica Signal Installation Guide.
6	Change the Oracle Empirica Signal application session timeout to be longer than the SSO session timeout.	Customer	Oracle Health Sciences Empirica SignalInstallation Guide.
7	Configure the Oracle Empirica Signal application server for native logins.	Customer	Oracle Health Sciences Empirica Signal Installation Guide.
8	Restart the Oracle Empirica Signal service.	Customer	Oracle Health Sciences Empirica Signal Installation Guide.
9	Validate SSO by logging in with your SSO user name and password.	Customer	Oracle Health Sciences Empirica Signal Installation Guide.
10	Create SSO users in the SSO application.	Customer	Oracle Access Manager documentation.
11	Rename existing Oracle Empirica Signal user names to match their associated SSO user names, or create new users as necessary.	Customer	Rename a user Add or edit a user
12	Select SSO in the Authentication drop-down list for users and user profiles.	Customer	Add or edit a user Add or editing a user profile