Skip to main content

Aha! (IdP-initiated) Integration Guide

Introduction

Use this guide to enable 2-Factor Authentication and Single Sign-on (SSO) access via SAML to Aha!.

Prerequisites

1. Have an Aha! account

2. Create a New Realm for the Aha! integration

3. Configure the following tabs in the Web Admin before configuring the Post Authentication tab:

  • Overview – the description of the realm and SMTP connections must be defined

  • Data – an enterprise directory must be integrated with SecureAuth IdP

  • Workflow – the way in which users will access this application must be defined

  • Multi-Factor Methods – the Multi-Factor Authentication methods that will be used to access this page (if any) must be defined

SecureAuth IdP Configuration Steps

Data

44831962.png

1. In the Profile Fields section, map the directory field that contains the user's Aha! ID to the SecureAuth IdP Property

For example, add the Aha! ID directory attribute to the Email 2 Property if it is not already contained somewhere else

Warning

Click Save once the configurations have been completed and before leaving the Data page to avoid losing changes

Post Authentication

44831397.png

2. In the Post Authentication section, select SAML 2.0 (IdP Initiated) Assertion Page from the Authenticated User Redirect dropdown

3. An unalterable URL will be auto-populated in the Redirect To field, which will append to the domain name and realm number in the address bar (Authorized/SAML20IdPInit.aspx)

User ID Mapping

60564688.png

4. Select the SecureAuth IdP Property that corresponds to the directory field that contains the Aha! ID (Email 2)

5. Select urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified from the Name ID Format dropdown (default)

Select a different option if Aha! requires it, which the Service Provider (SP) provides

SAML Assertion / WS Federation

44831964.png

6. Set the SAML Consumer URL to https://<company>.aha.io/auth/saml/callback

7. Set the WSFed/SAML Issuer to a Unique Name that will be shared with Aha!

The WSFed/SAML Issuer must match exactly on the SecureAuth IdP side and the Aha! side

8. Set the SAML Audience to https://<company>.aha.io/

9. Set the SAML Offset Minutes to make up for time differences between devices

10. Set the SAML Valid Hours to limit for how long the SAML assertion is valid

Note

No configuration is required for the WSFed/SAML Target URL, SAML Recipient, or SP Start URL fields

70489017.png

11. Leave the Signing Cert Serial Number as the default value, unless there is a third-party certificate being used for the SAML assertion

If using a third-party certificate, click Select Certificate and choose the appropriate certificate

12. Download the Assertion Signing Certificate to be used in the Aha! integration

13. Provide the Domain in order to Download the Metadata File to send to Aha! (if required)

Warning

Click Save once the configurations have been completed and before leaving the Post Authentication page to avoid losing changes

Forms Auth / SSO Token

Optionally, in the Forms Auth / SSO Token section, click the View and Configure FormsAuth keys/SSO token link to configure the token/cookie settings and configure this realm for SSO.

44833086.png

Aha! Configuration Steps

Contact Aha! to enable the application for 2-Factor Authentication and SSO

Note

Typical Information Required by SP

IdP URL is the Fully Qualified Domain Name (FQDN) of the SecureAuth IdP appliance, followed by the application-integrated realm, e.g. https://secureauth.company.com/secureauth2/secureauth.aspx

Issuer is the same Unique Name set in the SecureAuth IdP Web Admin

SAML Certificate is the Assertion Signing Certificate in the SecureAuth IdP Web Admin

Download the certificate, and either upload the file to the application or copy the contents of the certificate and paste them into a field

In this section: