• Overview
  • Configuration

Related-apps

Admina

How to configure Admina extension in ADManager Plus

Identity ProvisioningIdentity Management

The Money Forward Admina extension for ADManager Plus brings identity-driven automation to SaaS management. Admina provides centralized visibility into SaaS usage, license allocation, and shadow IT across cloud applications. By extending ADManager Plus to Admina, organizations can align SaaS access with authoritative identity data from Active Directory.

With this extension, user life cycle changes in Active Directory, such as onboarding, role changes, or offboarding, can automatically trigger corresponding account actions in Admina. This ensures SaaS access remains accurate, up to date, and policy-compliant without manual intervention. IT teams gain tighter control over SaaS environments, reduced operational overhead, and improved governance, while maintaining a single source of truth for user identities.

 

Automate SaaS access life cycle

Provision, update, or disable SaaS user access in Admina based on AD life cycle events.

 

Maintain identity consistency

Keep user identities and access status aligned between Active Directory and Admina.

 

Reduce risk and admin effort

Eliminate manual user management, prevent stale access, and strengthen SaaS governance.

 

How to configure Admina extension in ADManager Plus

Prerequisites:

Please ensure to provide the Bearer Token to retrieve desired information and perform tasks in Admina. Refer to Admina 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 Admina (outbound action): Ensure the account used for authorization has permission to perform the desired action.

Note: ADManager Plus comes with a preconfigured set of APIs that helps perform basic actions with the extension. If the action you require is not available, please gather the necessary API details from the Admina API documentation to configure under the inbound/outbound webhooks to perform the required actions.

Installing an extension in ADManager Plus

  • Log in to ManageEngine Marketplace
  • Under ADManager Plus, select Admina.
  • Click the Download button to download the extension Zip file.
  • Log in to ADManager Plus and navigate to the Admin tab.
  • In the left pane, under Marketplace, click Extensions.
  • Navigate to the Install Extension tab in the top right.
  • In the Install Extension dialog, click Browse.
  • Select the downloaded .ext file from your local system.
  • Click Continue to Install to proceed with the installation.
  • Once the installation is complete, verify that the extension appears in the installed extensions list.

Authorization configuration

  • Log in to ADManager Plus and navigate to Directory/Application Settings.
  • Go to Application Integrations, then search and select Admina.
  • Toggle the Enable Admina Integration button to On.
  • In the Admina Configuration page, click Authorization.
  • Perform the steps to generate Bearer Token in Admina and paste the Bearer Token in the Value field.
  • Enter the API Key in the Authorization value.
  • Click Configure.

Inbound webhook configuration

Inbound webhook enables you to fetch user data from Admina and transfer it 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 Admina:

  • Under Inbound Webhook, click Admina Endpoint Configuration.
  • In the Endpoint Configuration tab, an endpoint, Admina Get Organization Users ENDPOINT, comes preconfigured with an Endpoint URL, API Method, Headers, and Parameters fields to fetch user accounts from Admina. If you would like to use this preconfigured endpoint, replace {organizationId} with your Organization ID when fetching org users and replace {OrganizationID} and {UserID} with the respective values for user updates. Use token placeholder {Admina_APIKey}. 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 Admina's API references. Click here to learn how. Note:
    • The API key value pair is preconfigured as a header for authenticating API requests as structured during Authorization Configuration.
    • You can add macros to your endpoint configuration to dynamically change it as per your requirement using the macro chooser component.
    • Refer to Admina'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 Admina's API references to know the Parameters that must be configured to fetch only specific parameters.
    • You can configure multiple endpoints for Admina 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 Admina.
  • 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. Note: When multiple endpoints are configured, this attribute must hold the same value in all the endpoints.
    • In the Attribute Mapping field, select the attribute from the LDAP Attribute Name drop-down menu and map it with the respective attribute in Admina.
    • If you would like to create a new custom format for this, click Add New Format.
    • 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

An outbound webhook enables you to send changes made in AD using ADManager Plus to Admina and carry out tasks in Admina, all from ADManager Plus. To configure an outbound webhook for Admina:

  • Under Outbound Webhook, click Admina 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 Admina's API references for the API details, such as the URL, headers, parameters, and other requirements.
  • 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 and 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 ).