Aha cloud application

You must be signed in as a super administrator for this task.

Using Security Assertion Markup Language (SAML), your users can use their Google Cloud credentials to sign in to enterprise-cloud applications.

Set up SSO via SAML for Aha

Here's how to set up single sign-on(SSO) via SAML for the Aha application.

Step 1: Set up Google as a SAML identity provider (IdP)
  1. Sign in to your Google Admin console.

    Sign in using an account with super administrator privileges (does not end in @gmail.com).

  2. From the Admin console Home page, go to Appsand thenWeb and mobile apps.
  3. Click Add appand thenSearch for apps.
  4. Enter Aha in the search field.
  5. In the search results, hover over the Aha SAML app and click Select.
  6. On the Google Identity Provider details page, download the IDP metadata.
  7. Click Continue.
  8. On the Service provider details page, edit the ACS URL and Entity ID,  replacing {your‑domain} with your domain name.
  9. Click Continue.
  10. On the Attribute Mapping page, click the Select field menu and map the following Google directory attributes to their corresponding Aha attributes:
     
    Google directory attribute Aha attribute
    Basic Information > Primary Email EmailAddress
    Basic Information > First Name FirstName
    Basic Information > Last Name LastName
  11. Click Finish.
Step 2: Set up Aha as a SAML 2.0 service provider (SP)
  1. Open a new incognito browser window.
  2. Sign in to https://{your_domain}.aha.io.com with your organization's Aha administrator account.
  3. From the Aha home page, click the Settings icon at upper right, then click Account.
  4. In the left menu, click Security and single sign-on.
  5. For Identity provider, choose SAML 2.0.
  6. For Name, enter 'Gsuite'.
  7. For Configure using, click Metadata file.
  8. Next to Metadata file, click Choose File, then locate and select the IDP metadata file you downloaded in Step 1 above.
  9. Click Enable.
Step 3: Enable the Aha app
  1. Sign in to your Google Admin console.

    Sign in using an account with super administrator privileges (does not end in @gmail.com).

  2. From the Admin console Home page, go to Appsand thenWeb and mobile apps.
  3. Select Aha.
  4. Click User access.
  5. To turn on or off a service for everyone in your organization, click On for everyone or Off for everyone, and then click Save.

  6. (Optional) To turn a service on or off for an organizational unit:

    1. At the left, select the organizational unit.
    2. Select On or Off.
    3. Click Override to keep your setting if the service for the parent organizational unit is changed.
    4. If Overridden is already set for the organizational unit, choose an option:
      • Inherit—Reverts to the same setting as its parent.
      • Save—Saves your new setting (even if the parent setting changes).

    Learn more about organizational structure.

  7. (Optional) Turn on the service for a group of users.
    Use access groups to turn on a service for specific users within or across your organizational units. Learn more

  8. Ensure that your Aha user account email IDs match those in your Google domain.
Step 4: Verify that the SSO is working

Aha supports both Identity Provider (IdP) initiated and Service Provider (SP) initiated SSO. Follow these steps to verify SSO in either mode:

IdP-initiated

  1. Sign in to your Google Admin console.

    Sign in using an account with super administrator privileges (does not end in @gmail.com).

  2. From the Admin console Home page, go to Appsand thenWeb and mobile apps.
  3. Select Aha.
  4. At the top left, click Test SAML login

    Aha should open in a separate tab. If it doesn’t, use the information in the resulting SAML error messages to update your IdP and SP settings as needed, then retest SAML login.

SP-initiated

  1. Close all browser windows.
  2. Open https://{your_domain}.aha.com and attempt to sign in. You should be automatically redirected to the Google sign-in page.
  3. Enter your username and password.

After your sign in credentials are authenticated, you are automatically redirected back to Aha.



Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.
Was this helpful?
How can we improve it?