Aha! Roadmaps | Portal SSO | Link portal users to organizations (Advanced plan)

If you are using Salesforce community as your SAML identity provider

You will need to update your SAML configuration within Salesforce to include specific attributes.

• organization_ids: This should be set to the 18-character Salesforce account_id that users belong to. These can be multiple account_ids separated by a semicolon.

• salesforce_integration_id: Use the Aha! ID you use for your Salesforce integration.

With this configured, users who log in to your portal through SSO will be assigned to the organization in Aha! Ideas that is linked to the matching Salesforce account ID.

• If the portal user is already connected to a different Aha! organization, the new organization assignment from SSO will override it.

• If an organization with a matching account ID does not already exist in Aha! Ideas, a new one will be created and linked to Salesforce.

You may need to update attributes in an Apex plugin class for your SAML connected app. You can read Salesforce's instructions on adding custom attributes to a connected app or use the following code snippet to add the AccountID to SAML attributes for community users:

global class MyConnectedAppPlugin extends Auth.ConnectedAppPlugin { global override Map<String,String> customAttributes(Id userId, Id connectedAppId, Map<String,String> formulaDefinedAttributes, Auth.InvocationContext context) { // Get the user's associated contact User u = [SELECT Id, ContactId FROM User WHERE Id = :userId]; if(u.ContactId != null){ Contact c = [SELECT AccountId FROM Contact WHERE Id = :u.ContactId]; // Add the AccountId to your custom attributes map formulaDefinedAttributes.put('organization_ids', c.AccountId); } formulaDefinedAttributes.put('salesforce_integration_id', 'SALESFORCE_INTEGRATION_ID'); return formulaDefinedAttributes; } }

Top