• Overview
  • Configuration

Aha!

Streamline onboarding Aha! and ADManager Plus integration

Project management Identity provisioning

Aha! is product roadmap and project management software that product development teams use to plan, prioritize, and track product development initiatives. By integrating Aha! with Active Directory (AD) using ManageEngine ADManager Plus, IT teams can automate user provisioning processes. By automating key user management tasks, the integration keeps both platforms synchronized, ensuring that user roles and access permissions are always accurate and up to date.

 

Automated user provisioning

When a new team member is added to Aha!, their corresponding user account can be automatically created in AD, ensuring that they have access to the necessary systems and tools.

 

Enhanced security and compliance

Synchronizing user data between AD and Aha! ensures that access rights are accurately managed, minimizing the risk of unauthorized access.

 

Marketplace document: ADManager Plus - Aha! integration

Prerequisites

Aha! uses OAuth2.0 to authorize API requests. You'll need to have the client_id and client_secret to retrieve desired information and perform tasks in Aha!. Refer to Aha!'s API documentation 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 Aha! (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 integration. If the action you require is not available, please gather the necessary API details from Aha!'s API documentation to configure inbound or outbound webhooks to perform the required actions.

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 Aha!.
  • Toggle the Enable Aha! Integration button on.
  • On the Aha! Configuration page, click Authorization.
  • Perform the steps to generate a client_id and client_secret in Aha! and paste the bearer token in the Value field.
  • Click Configure.

Inbound webhook configuration

Inbound webhooks enable you to fetch user data from Aha! and send 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 Aha!:

  • Under Inbound Webhook , click Aha! Endpoint Configuration.
  • If you would like to use a preconfigured endpoint, replace {company} with the company name of your Aha! 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 Aha!'s API documentation. 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 requirements using the macro chooser component.
    • Refer to Aha!'s API documentation 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 Aha!'s API documentation to view the parameters that must be configured to fetch only specific parameters.
    • You can configure multiple endpoints for Aha! 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 Aha!.
  • 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., employeeIdentifier).
  • 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 Aha!.
    • If you would like to create a new custom format for this, click Add New Format.
    • Click Save.

    Outbound webhook configuration

    Outbound webhooks enable you to send changes made in AD to Aha! and carry out tasks in Aha!—all from ADManager Plus. The webhooks configured in this section can be included in orchestration templates, which in turn can be used during event-driven and scheduled automations. They can also be applied directly to desired users to perform a sequence of actions on them (Management > Advanced Management > Orchestration).

    To configure outbound webhooks for Aha!:

    • Under Outbound Webhook , click Aha! 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 Aha!'s API documentation 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 and Save.
    • A pop-up window will then display a list of AD users and groups to test the configured API call. Select the desired user or group over 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 as per the configuration.
    • The webhook response and request details will then be displayed. Verify them for the expected API behavior and click Save.