• Overview
  • Configuration

Related-apps

Articulate(Reach-360)

Streamline learner access in Articulate by automating directory provisioning.

Identity provisioningKnowledge management

Overview

Articulate Reach-360 is a cloud-based learning delivery platform that enables organizations to assign, track, and manage training for internal and external audiences. It supports SCORM and xAPI standards. Connecting Reach-360 with ADManager Plus ensures that training access is automatically granted and revoked based on changes in Active Directory, reducing friction and improving compliance.

Use cases

 

Provisioning

Provision new learner accounts in Reach-360 based on AD user onboarding workflows.

 

Revoke

Revoke access to Reach-360 automatically when a user is disabled in Active Directory.

 

Synchronization

Keep learner profiles synchronized by mapping fields like email, role, or department from AD to Reach-360.

 

Prerequisites:

Please ensure to provide the bearer token to retrieve desired information and perform tasks in Reach 360. Refer to Reach 360 API references for more details.

Privileges:

  • To import users (inbound action): Ensure the account used for authorization has permission to read all user accounts.
  • To perform any action or query in Reach 360 (outbound action): Ensure the account used for authorization has permission to perform the desired action.

Authorization configuration

  • Log in to ADManager Plus and navigate to the Automation tab.
  • In the left pane, under Configuration, click Application Integrations.
  • Under Enterprise Applications, click Reach 360.
  • Toggle the Enable Reach 360 Integration button on.
  • In the Reach 360 Configuration page, click Authorization.
  • Perform the steps to generate Bearer token in Reach 360 and paste the Bearer token in the Value field.
  • Click Configure.

Inbound webhook configuration

Inbound webhook enables you to fetch user data from Reach 360 to ADManager Plus.The attribute mapping configured in this section can be selected as the data source during automation configuration.

To configure an inbound webhook for Reach 360:

  • Under Inbound Webhook, click Reach 360 Endpoint Configuration.
  • In the Endpoint Configuration tab, an endpoint, Reach 360 USERS ENDPOINT, comes pre-configured with an Endpoint URL, API Method, Headers, and Parameters fields to fetch user accounts from Reach 360. If you would like to use this preconfigured endpoint, replace {yourdomain} with that of your Reach 360 instance in the Endpoint URL field. However, if you would like to use a new endpoint to import users, you can configure one using the + Add API endpoint button and filling in the required fields as per Reach 360’s API references. Click here to learn how. Note:
    • The API key value pair is preconfigured as a header for authenticating API requests as configured during Authorization Configuration.
    • Macros: You can add macros to your endpoint configuration to dynamically change it as per your requirement using the macro chooser component. Refer to Reach 360's API references and configure additional headers and parameters, if required.
  • Once done, click Test & Save. A response window will display all the requested parameters that can be fetched using the API call. After verifying if the requested parameters have been called to action, click Proceed. Note:
    • Refer to Reach 360’s API references to know the Parameters that must be configured to fetch only specific parameters.
    • You can configure multiple endpoints for Reach 360 using the + Add API endpoint button. Click here to learn how.
  • Click Data Source - LDAP Attribute Mapping to match endpoints and to map AD LDAP attributes with the respective attributes in Reach 360.
  • Click + Add New Configuration and perform the following:
    • Enter the Configuration Name and Description, and select the Automation Category from the drop-down menu.
    • In the Select Endpoint field, select the desired endpoint and a Primary Key that is unique to a user (e.g., id).
    • In the Attribute Mapping field, select the attribute from the LDAP Attribute Name drop-down menu and map it with the respective column in Reach 360.
    • If you would like to create a new custom format for this, click Mapping Attribute.
    • Click Save.
Note: The attribute mapping configured in this section can be selected as the data source during automation configuration to perform the desired action on the list of users received from the API response

Outbound webhook configuration

Outbound webhook enables you to update the changes made in AD using ADManager Plus to Reach 360 or fetch or forward required details from Reach 360 and synchronize them with AD. They can also be applied directly to desired users to perform a sequence of actions on them.

To configure an outbound webhook for Reach 360:

  • Under Outbound Webhook, click Reach 360 Webhook Configuration.
  • Click + Add Webhook.
  • Enter a name and description for this webhook.
  • Decide on the action that has to be performed and refer to Reach 360’s API references for the API details, such as the URL, headers, parameters, and other requirements that will be needed.
  • Select the HTTP method that will enable you to perform the desired action on the endpoint from the drop-down menu.
  • Enter the endpoint URL.
  • Configure the Headers, Parameters, and Message Type in the appropriate format based on the API call that you would like to perform.
  • Click Test & Save.
  • A pop-up window will then display a list of AD users and groups on which to test the configured API call. Select the desired user or group on which this API request has to be tested and click OK. This will make a real-time call to the endpoint URL, and the selected objects will be modified according to the configuration.
  • The webhook response and request details will then be displayed. Verify them for the expected API behavior and click Save.
Note: The webhooks configured in this section can be included in Orchestration Templates, which can be used in event-driven and scheduled automations. They can also be applied directly to desired users to perform a sequence of actions on them (under Management > Advanced Management > Orchestration).