1 Introduction

Starting with Oracle Empirica Signal version 8.0, Oracle Health Sciences Empirica Signal is integrated with Oracle Health Sciences Identity and Access Management Service.

Oracle Health IAMS manages user credentials and controls if a user can log into a particular Cloud application or environment. In Oracle Health IAMS, each user has a single username and password. These are valid across all enabled OHS Cloud Services, regardless of the number of different applications or environments the user has access to.

Each company that uses OHS Cloud Services nominates at least one Customer Delegated Administrator (CDA). This individual can create, enable or disable, or lock user accounts as well as define which applications and Cloud environments a user can access.

Even though Oracle Health IAMS manages the user accounts, application-specific user roles and privileges are still defined in an application's administrative user interface (UI). For Oracle Empirica Signal, the person who assigns roles and privileges to users is typically the Oracle Empirica Signal Customer Administrator.

The Oracle Empirica Signal Customer Administrator can be the same person as the Oracle Health IAMS CDA or a different individual. This guide describes both tasks that require the Oracle Health IAMS CDA role, and tasks that require the Customer Administrator or super-user Oracle Empirica Signal application role.

The process to create accounts is different for new and upgraded users. As a result, before the CDA creates a new Oracle Health IAMS account, the CDA must determine if that user has used the Oracle Empirica Signal Cloud environment previously.

Upgraded users have existing application accounts in Oracle Empirica Signal. The CDA must review or update the details of the Oracle Empirica Signal accounts to match Oracle Health IAMS naming conventions. For details on how to update existing application accounts, please see Adjust the user's Oracle Empirica Signal account details.

There are two workflows for notifying a user that the Oracle Health IAMS account has been created:

1. Security questions: The user receives two emails. One says that the user has an account, and the other provides a temporary password. The user is expected to log in, set the answers to the security questions, and change the password.
2. Email link: The user receives one email that contains both the information that the account has been created and a link to set the initial password.

Which workflow is followed depends on how the Oracle Health IAMS tenant has been configured. For example, a newly set-up tenant follows the email link workflow. If you are adding a user to an old tenant, you will likely use the security questions workflow, unless the CDA has opted in to using the email link workflow.