NameID in a Custom Aha! SAML Application
May 27, 2025
Single Sign-On
Okta Classic Engine
Okta Identity Engine
Overview
This article talks about the Aha! Custom SAML Application that needs to have the NameID as something else apart from email address.
Applies To
- Aha! Custom Application
- The NameID needs to be different than the email address.
- Security Assertion Markup Language (SAML)
- Okta Integration Network (OIN)
Cause
The OIN applications do not allow SAML settings changes besides the username format and additional attribute statements.
Based on the Aha! documentation - NameID: Each user in the Aha! account needs to have a unique NameID. This value must be unique — an email address cannot be used as a NameID. This ensures that any changes to a user's email address can be reflected in the Aha! account.
Solution
To solve this, create a custom application. Go to the General tab > hit next to Configure SAML > Change the Application username to Custom and apply the custom expression:
user.getInternalProperty("id")
See screenshot below:
