Integrate Lucid SAML SSO with Active Directory Federation Services (ADFS)

Download the federation metadata and import it into Lucid

1. Download the federation metadata. 
   • The federation metadata can be accessed on the ADFS server at the following URL, replacing [myserver.domain] to reflect your ADFS server URL:
     https://[myserver.domain].com/FederationMetadata/2007-06/FederationMetadata.xml
2. Navigate to the Lucid admin panel.
3. Select the App Integration tab.
4. In the App integration drop-down, select General.
5. Click Settings in the "SAML" integration tile.
6. Upload the XML metadata to Lucid using the file picker.
   • Note: If you have this in text format please save it as an XML file then upload it to Lucid.

Configure the Lucid Relying Party Trust in ADFS

Next, create and configure a Relying Party Trust using the Lucid metadata. 

1. From the Lucid SAML page, select Download Metadata to download the Lucid metadata.
2. Save the metadata in a location accessible to the ADFS server.
   
3. Open ADFS and right click Relying Party Trust.
4. Select Add Relying Party Trust from the menu to open the Add Relying Party Trust Wizard.
   
5. Click through the Welcome screen prompts.
6. On the Select Data Source screen, select Import data about the relying party from a file.
7. Select Browse and locate the Lucid metadata file.
8. Complete the remaining settings based on your organization's preferences.
   
9. Open the Endpoints configuration for your Lucid relying party trust. 
   • You will need to add another endpoint to accommodate for ADFS storing the incoming sign-on URL against the supplied ACS/reply URL. The settings should be:
     • Type = SAML Consumer Assertion
     • Binding = POST
     • Index = 1

     • Trusted URL = https://www.lucidchart.com/saml/sso/IDP Entity ID

     • Once finished the configuration will look like this:
       
10. Right-click the Lucid Relying Party Trust and select Edit Claim Rules.
11. Add a claim rule using LDAP and configure the claim rule to match the attributes and claim types shown below.
    
12. Click Finish.

Now you have completed the ADFS SAML integration in Lucid and your Lucid account will support SAML single sign-on authentication through ADFS.

You have the option to use encrypted assertions for the identity providers you add for SAML to your Lucid account.To learn more, refer to our SAML overview article.

Troubleshooting: ADFS integration set up

Invalid SAML Response
This error corresponds with an incorrect SAML response from the IDP. It usually means that the hash algorithm needs to be switched from “SHA-1” to “SHA-256” in ADFS. Navigate to the Lucid Relying Party Trust, right click, and select “Properties.” Click the Advanced tab and switch the hash algorithm from “SHA-1” to “SHA-256.”

SAML is not configured for your team. Request an invite from a SAML enabled team.
This error appears when a user attempting to log in through SAML is not associated with the SAML enabled team. The admin will need to send an invite to the user to be accepted to the team. From the Lucid Admin Panel, select “Users.” Click “+User” in the top right corner and enter the user’s email.

Invalid Identity Attribute
This error indicates that an invalid identity attribute was received in the SAML response. Configure a claim attribute for the Lucid Relying Party Trust where “Email-Addresses” corresponds to “Name ID” in ADFS.

Could Not Parse XML
This error indicates an incorrect syntax in the identity provider XML metadata. This can happen when downloading metadata from an Internet Explorer window. Internet Explorer will add dashes to XML tags for expanding and collapsing. You can fix this issue by either opening the XML data in a text editor or deleting all of the dashes in the copied XML text.

username_12345@example.com Users Being Created
The Lucid SAML integration accepts 3 attributes: First Name, Last Name, and Email Address. When an invalid email address is passed from the SAML identity provider, a valid email will be generated to create the user: “passed value” + “SAML ID” + “@example.com.” This often occurs when a username or given name is passed to the Email Address attribute instead of the valid email. You can resolve this issue by configuring your claim rule to send a valid email address in the Email Address attribute.

ADFS does not return a response to Lucid
Check the Endpoints to make sure you followed the steps listed in the ADFS set up steps. If you just have a single endpoint or have your www. endpoint indexed before your app. endpoint, the response will not make it back to Lucid.

Give feedback on this article