Microsoft Active Directory Federation Services

You can use Microsoft Active Directory Federation Services (ADFS) as an identity provider for users in your Aha! account based on . You will need to be an in your Aha! account and an administrator in ADFS to configure SSO.

Click any of the following links to skip ahead:

In ADFS
In your Aha! account
User attributes
Troubleshooting

In your Aha! account

Log into your Aha! account and go to Settings ⚙️ Account Security and single sign-on Single sign-on.
Select SAML 2.0 as your Identity provider.
Name your configuration.
For the Metadata URL, enter the URL to the metadata xml listed in AD FS 2.0 console, e.g. https://adfs.<company>.com/FederationMetadata/2007-06/FederationMetadata.xml.
Enter the remaining fields following the SAML 2.0 configuration instructions.

Top

In ADFS

In Server Manager, click Tools AD FS Management.
Click Add Relying Party Trust under Actions. This will open the Add Relying Party Trust Wizard.
In the Welcome step, click Claims aware, then Start.
In the Select Data Source step, choose Import data about the relying party, then enter your Aha! account URL in the Federation metadata address field. The URL should be in the following format: https://<accountname>.aha.io/auth/saml/metadata.
The metadata URL will only work once SAML authentication is enabled in your Aha! account.
In the Specify Display Name step, name your relying party (e.g. "Aha!").
The Configure Certificate step is optional. Click Next.
The Configure URL step is optional. Click Next.
In the Configure Identifiers step, enter your Aha! account URL in the following format: https://<accountname>.aha.io.
In the Choose Access Control Policy step, choose to Permit everyone.
Review your settings on the Ready to Add Trust step, then click Next.
On the Finish step, click Close. This will open the Edit Claim Rules modal.
On the Issuance Transform Rules tab, click Add Rule....
Select the Send LDAP Attributes as Claims template.
Click Next. Name your rule, select Active Directory as the attribute store, and then add the following mappings:
LDAP Attribute
Outgoing Claim Type
NameID
NameID
Given-Name
Given Name
Surname
Surname
Each user in your Aha! account needs to have a unique NameID. This value must be unique — an email addresses cannot be used as a NameID. This ensures that any changes to a user's email address can be reflected in your Aha! account.
Click OK.
On the Issuance Transform Rules tab, click Add Rule... again.
Select the Transform an Incoming Claim template, then click Next.
Name the rule and make the following selections:
1. Incoming claim type: NameID
2. Outgoing claim type: NameID
3. Outgoing name ID format: Unspecified
4. E-Mail Address: E-Mail Address
5. Pass through all claim values
Click OK.

Top

Troubleshooting

We have created an article to help you , complete with explanations and resolutions.

The best place to start in most of these situations is the Recent SSO events for your SSO configuration, at the bottom of the configuration page. Those messages will help diagnose and solve the problem.

Top

If you get stuck, please reach out to our Customer Success team. Our team is made up entirely of product experts and responds fast.

Suite overview

Billing and users

Security and system requirements

Single sign-on (SSO)

SAML 2.0

Google Cloud Identity

Microsoft Entra ID

OneLogin

Bitium

Microsoft Active Directory Federation Services