Explore  

This article discusses functionality that is included in the Aha! Knowledge Advanced plan. Please contact us if you would like a live demo or want to try using it in your account.

Aha! Knowledge | Microsoft Active Directory Federation Services (ADFS)

You can use Microsoft Active Directory Federation Services (ADFS) as an identity provider for your knowledge base with SAML 2.0. You will need to have administrator with account permissions in your Aha! account and in ADFS to configure SSO.

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 knowledge base 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 knowledge base URL.

  • 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.

Top

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.

Top

Suite overview
Aha! Roadmaps
Aha! Ideas