Integrate OpenSesame with Oracle Learning

Complete this one-time setup to configure integration, enable secure data exchange, and start importing, tracking, and managing OpenSesame learning in Oracle Learning.

1. Make sure that you have an active account with OpenSesame that allows integrations.
2. Configure Single Sign On between Oracle Learning and OpenSesame to ensure the correct exchange of user information for learner progression tracking. You can use any identity provider.
3. Enable self-paced learning.
4. In Oracle Cloud Infrastructure Identity and Access Management, generate a unique set of Oracle client ID, client secret, token URL or OAuth server URL, and scope for each POD where you're enabling integration. The set lets you authenticate incoming requests from OpenSesame to track learning completions.
   1. Sign in to Oracle Cloud console.
   2. On the navigation menu, select Identity & Security > Domains.

      Complete steps c through l as many times as you have PODs. For example, to enable integration in a development POD and a production POD, complete the steps twice.

   3. On the Integrated applications tab, add a confidential application for OpenSesame.
   4. Enter a unique name that includes OpenSesame for easy identification, such as OpenSesame dev or OpenSesame prod, and a description.
   5. Submit the application.
   6. In the Configure OAuth step, configure the app as a client now.
   7. For authorization, select Client credentials.
   8. In the Token issuance policy section, add specific authorized resources that are accessible to the users.
   9. Add the Oracle Applications Cloud (Fusion) scope.

      The description shows the scope in the format <resource audience><resource scope>, for example, urn:opc:resource:fa:instsanceid=630113349urn:opc:resource:consumer::all. Copy this scope, which is different for each of your environments, because you'll need to share this information with OpenSesame.

   10. Submit the configuration.
   11. Review the configuration and activate the app.
   12. From the OAuth configuration page of your activated app, copy the client ID and client secret values because you need to share this information with OpenSesame.
5. In Oracle, create a job role that includes only the Learning Content Provider duty role--don't include any other duty role. The role lets this account use the necessary Oracle APIs to receive content and completions from OpenSesame.
   1. Go to Tools > Security Console.
   2. On the Roles tab, create your job role.
   Caution: If you have any IP restrictions or have enabled location-based access control (LBAC), make sure to enable the job role for access from all IP addresses. Otherwise OpenSesame will get API authentication failures when sending content to Oracle Learning.
6. Configure the Oracle client ID from step 4 as a user account that you'll use in step 7.
   1. On the security console Users tab, add a user account.
   2. Set Associated Person Type to None. Make sure the user isn't associated with a person or worker account.
   3. Enter the appropriate user details so you can identify the account. Make sure that the user name is the same as the Oracle client ID value. Any discrepancy might lead to an unsuccessful configuration.
   4. Add the job role that you created in step 5.
7. Enable OpenSesame.
   1. Go to My Client Groups > Learning and Development > Configure External Providers.
   2. Configure OpenSesame and enter the user account created in step 6.
   3. Select a learning catalog profile to apply to all imported OpenSesame learning. The profile identifies who can see and manage the learning.
   4. Optional: Configure audience and catalog settings. The settings apply to new content imported after you validate your changes. Changes aren't automatically applied to content imported before you validate these changes.
   5. Validate the configuration.
   6. Optional: Change the attribute mappings between certain OpenSesame attributes and Oracle Learning attributes that you might have extended or changed.
8. If they're not already scheduled because another provider is already enabled or you've been creating and managing your own self-paced learning, schedule these background processes.
   1. Go to Tools > Scheduled Processes.

   Process	Input parameter	Recommended frequency	Description
   ESS job to run Bulk ingest to OSCS	Program Name is OLC-REST	Once per day, after the Load and Synchronize External Course Data process completes	Make new content and updates visible to people in Oracle Learning
   Process Learning Experience Statements	NA	Once per day	Process any learner experience statements that for some reason weren't processed immediately
   Process Learning Experience Statements	NA	Once per day, after the Load and Synchronize External Course Data process completes	Deactivate content and withdraw active enrollments

9. If you set the provider content visibility to private, schedule the Reconcile User Groups background process to run daily if it's not already scheduled.