This article discusses functionality that is included in the Aha! Ideas Advanced plan. Please contact us if you would like a live demo or want to try using it in your account.
Aha! Roadmaps | Portal SSO | Microsoft Active Directory Federation Services (ADFS)
You can use Microsoft Active Directory Federation Services (ADFS) as an identity provider for ideas portal users in Aha! Roadmaps based on SAML 2.0. You will need to be an administrator in Aha! Roadmaps and in ADFS to configure SSO.
If you have multiple ideas portals and want to use a single ADFS single sign-on configuration between all of them, you may be interested in the Ideas Advanced plan.
Click any of the following links to skip ahead:
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! Roadmaps account URL in the Federation metadata address field. You can copy it from the Aha! Roadmaps ideas portal SSO settings by navigating to Users SSO.
The metadata URL will only work once SAML authentication is enabled in your Aha! Roadmaps account.
In the Specify Display Name step, name your relying party (e.g. "Aha! Roadmaps").
The Configure Certificate step is optional. Click Next.
The Configure URL step is optional. Click Next.
In the Configure Identifiers step, enter your Aha! Roadmaps account URL. You can copy it from the Aha! Roadmaps ideas portal SSO settings by navigating to Users SSO.
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, press 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:
Incoming claim type: NameID
Outgoing claim type: NameID
Outgoing name ID format: Email
Pass through all claim values
Click OK.
In Aha! Roadmaps
Navigate to Settings ⚙️ Account Ideas Ideas portals or Ideas Overview. You will need to be an administrator with customizations permissions to configure an ideas portal.
From your account settings, click the name of the ideas portal you wish to edit.
From Ideas Overview, click the pencil icon by the name of the ideas portal you wish to edit.
Once you have your portal settings open, navigate to the Users tab, and the SSO section.
Choose SAML as your identity provider Type. Click Save.
The SAML 2.0 configuration will display.
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.
Click Enable SSO to complete the configuration.
Troubleshooting
We have created an article to help you troubleshoot common SSO configuration issues, 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.
It is possible to invite an ideas portal user from your ideas portal settings who has not been configured with the identity provider your portal is using. The user will not be able to log in to the ideas portal until they can be authenticated by the identity provider.
If you get stuck, please reach out to our Customer Success team. Our team is made up entirely of product experts and responds fast.