Advanced Operations

• 1: Setting Up Auth0 SAML for Single Sign-On
• 2: Setting Up AWS IAM Identity Center SAML for Single Sign-On
• 3: Setting Up Google Workspace SAML for Single Sign-On
• 4: Setting Up Microsoft Entra ID SAML for Single Sign-On
• 5: Setting Up Okta SAML for Single Sign-On
• 6: Manage Organization Administrators
• 7: Managing Single Sign-On for Organization
• 8: Setting Member Expiration Period

1 - Setting Up Auth0 SAML for Single Sign-On

PlaidCloud supports Single Sign-On (SSO) via SAML 2.0. This guide walks through configuring Auth0 as a SAML identity provider so your organization's users can authenticate through Auth0 when accessing PlaidCloud.

Prerequisites

• An Auth0 tenant
• An Auth0 account with the Administrator role
• Contact with PlaidCloud support to coordinate the setup and exchange configuration values

Overview

The setup process involves two parties exchanging SAML metadata:

1. You configure an application in Auth0 with the SAML2 Web App addon enabled and provide PlaidCloud with your Identity Provider Metadata URL.
2. PlaidCloud provides you with the Service Provider (SP) Entity ID and ACS URL (Assertion Consumer Service URL) needed to complete your Auth0 application configuration.

Coordinate with PlaidCloud support to obtain the SP values before completing Step 3 below.

Step 1: Create an Application

1. Sign in to the Auth0 Dashboard.
2. In the left sidebar, navigate to Applications > Applications.
3. Click Create Application.
4. Enter a name for the application (e.g., PlaidCloud SSO).
5. Select Regular Web Applications as the application type.
6. Click Create.

Step 2: Enable the SAML2 Web App Addon

1. On the application detail page, select the Addons tab.
2. Click the SAML2 Web App addon to enable it.
3. The addon settings panel will open. Leave it open — you will configure it in the next step.

Step 3: Configure SAML Settings

In the SAML2 Web App addon settings panel:

1. In the Application Callback URL field, enter the ACS URL provided by PlaidCloud.
2. In the Settings JSON editor, set the audience field to the SP Entity ID provided by PlaidCloud:

{
  "audience": "your-sp-entity-id-from-plaidcloud",
  "mappings": {
    "email": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress",
    "given_name": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname",
    "family_name": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname"
  },
  "nameIdentifierFormat": "urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress",
  "nameIdentifierProbes": [
    "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress"
  ]
}

3. Click Enable (or Save) to apply the settings.

Step 4: Retrieve and Send the Identity Provider Metadata URL

Once the addon is enabled, locate the metadata URL and send it to PlaidCloud so the integration can be completed.

1. In the SAML2 Web App addon settings panel, select the Usage tab.
2. Copy the Identity Provider Metadata URL (formatted as https://{your-auth0-domain}/samlp/metadata/{client-id}).

Send this Metadata URL to PlaidCloud support. This is the Entity Descriptor URL that PlaidCloud needs to configure the trust relationship on the identity provider side. Once PlaidCloud receives this URL, the team will complete the Keycloak configuration and notify you when SSO is ready to test.

Step 5: Configure Attribute Mappings for Groups (Optional)

If your PlaidCloud configuration uses group-based security role assignments, you can pass group membership through the SAML assertion using Auth0 rules or actions.

Using Auth0 Actions

1. In the left sidebar, navigate to Actions > Library.
2. Click Build Custom and create a new action for the Login / Post Login trigger.
3. Add logic to append group information to the SAML assertion. For example, if groups are stored as user metadata:

exports.onExecutePostLogin = async (event, api) => {
  const groups = event.user.app_metadata?.groups || [];
  api.samlResponse.setAttribute("groups", groups);
};

4. Deploy the action and add it to the Login flow.

Step 6: Control User Access

Auth0 controls which users can authenticate based on the connections and rules attached to the application.

1. On the application detail page, select the Connections tab.
2. Enable the appropriate connections (e.g., your organization's database connection, Active Directory, or social connections) for this application.
3. Disable any connections that should not have access to PlaidCloud.

To restrict access to specific users within a connection, use Auth0 Actions or Rules to allow or deny authentication based on user attributes or group membership.

Testing the Integration

After PlaidCloud confirms the configuration is complete:

1. Navigate to your organization's PlaidCloud Workspace (e.g., https://my-workspace.plaid.cloud).
2. You will be redirected to the Auth0 sign-in page (or your configured connection's login).
3. Sign in with your Auth0 credentials.
4. Upon successful authentication, you will be redirected back to PlaidCloud.

If you encounter errors, verify that:

• The Application Callback URL and audience match exactly what PlaidCloud provided
• The SAML2 Web App addon is enabled on the application
• The nameIdentifierFormat is set to the email address format
• The Metadata URL you sent to PlaidCloud is accessible
• The user's connection is enabled on the application

2 - Setting Up AWS IAM Identity Center SAML for Single Sign-On

PlaidCloud supports Single Sign-On (SSO) via SAML 2.0. This guide walks through configuring AWS IAM Identity Center (formerly AWS SSO) as a SAML identity provider so your organization's users can authenticate through AWS when accessing PlaidCloud.

Prerequisites

• An AWS account with IAM Identity Center enabled
• An IAM user or role with the AWSSSOMasterAccountAdministrator managed policy or equivalent permissions
• IAM Identity Center must be configured with an identity source (the built-in directory, Active Directory, or an external IdP)
• Contact with PlaidCloud support to coordinate the setup and exchange configuration values

Overview

The setup process involves two parties exchanging SAML metadata:

1. You configure a custom SAML application in IAM Identity Center and provide PlaidCloud with your SAML Metadata URL.
2. PlaidCloud provides you with the Service Provider (SP) Entity ID and ACS URL (Assertion Consumer Service URL) needed to complete your application configuration.

Coordinate with PlaidCloud support to obtain the SP values before completing Step 3 below.

Step 1: Create a Custom SAML Application

1. Sign in to the AWS Management Console and navigate to IAM Identity Center.
2. In the left sidebar, select Applications.
3. Click Add application.
4. Select I have an application I want to set up and choose Custom SAML 2.0 application.
5. Click Next.
6. Enter a Display name for the application (e.g., PlaidCloud SSO) and optionally a description.

Step 2: Retrieve the IAM Identity Center SAML Metadata URL

Before configuring the service provider details, locate your IAM Identity Center metadata URL to send to PlaidCloud.

1. On the application configuration page, scroll to the IAM Identity Center metadata section.
2. Copy the IAM Identity Center SAML metadata URL (formatted as https://portal.sso.{region}.amazonaws.com/saml/metadata/{instanceId}).

Send this Metadata URL to PlaidCloud support. This is the Entity Descriptor URL that PlaidCloud needs to configure the trust relationship on the identity provider side. Once PlaidCloud receives this URL, the team will complete the Keycloak configuration and notify you when SSO is ready to test.

Step 3: Configure Service Provider Details

1. Scroll to the Application properties section.
2. In the Application ACS URL field, enter the ACS URL provided by PlaidCloud.
3. In the Application SAML audience field, enter the SP Entity ID provided by PlaidCloud.
4. Click Submit.

Step 4: Configure Attribute Mappings

IAM Identity Center passes user attributes to PlaidCloud in the SAML assertion. Configure attribute mappings so PlaidCloud receives the necessary user details.

1. On the application detail page, select the Attribute mappings tab.
2. Click Add new attribute mapping and add the following:

3. Click Save changes.

Group Membership (Optional)

IAM Identity Center does not natively pass group membership as a SAML attribute in the same way as other providers. If your PlaidCloud configuration requires group-based security role assignments, discuss the available options with PlaidCloud support. Common approaches include using the built-in directory with group assignments or syncing groups from an external identity source such as Active Directory.

Step 5: Assign Users and Groups to the Application

Only users and groups assigned to the application will be able to authenticate through this SSO configuration.

1. On the application detail page, select the Assign users and groups tab.
2. Click Assign users and groups.
3. Search for and select the users or groups that should have SSO access to PlaidCloud.
4. Click Assign users.

Testing the Integration

After PlaidCloud confirms the configuration is complete:

1. Navigate to your organization's PlaidCloud Workspace (e.g., https://my-workspace.plaid.cloud).
2. You will be redirected to the AWS IAM Identity Center sign-in page.
3. Sign in with your AWS IAM Identity Center credentials.
4. Upon successful authentication, you will be redirected back to PlaidCloud.

If you encounter errors, verify that:

• The ACS URL and SP Entity ID match exactly what PlaidCloud provided
• The user attempting to log in is assigned to the application in IAM Identity Center
• The Subject attribute is mapped to ${user:email} with the emailAddress format
• The Metadata URL you sent to PlaidCloud is accessible from PlaidCloud's servers

3 - Setting Up Google Workspace SAML for Single Sign-On

PlaidCloud supports Single Sign-On (SSO) via SAML 2.0. This guide walks through configuring Google Workspace as a SAML identity provider so your organization's users can authenticate through Google when accessing PlaidCloud.

Prerequisites

• A Google Workspace account (Business Starter or higher)
• A Google Workspace account with the Super Admin role
• Contact with PlaidCloud support to coordinate the setup and exchange configuration values

Overview

The setup process involves two parties exchanging SAML metadata:

1. You configure a custom SAML app in Google Workspace and provide PlaidCloud with your IdP Metadata URL.
2. PlaidCloud provides you with the Service Provider (SP) Entity ID and ACS URL (Assertion Consumer Service URL) needed to complete your Google Workspace configuration.

Coordinate with PlaidCloud support to obtain the SP values before completing Step 3 below.

Step 1: Create a Custom SAML App

1. Sign in to the Google Admin console as a Super Admin.
2. Navigate to Apps > Web and mobile apps.
3. Click Add app > Add custom SAML app.
4. Enter a name for the app (e.g., PlaidCloud SSO) and optionally add a description and icon.
5. Click Continue.

Step 2: Retrieve the IdP Metadata URL

On the Google Identity Provider details screen, Google displays the identity provider information needed by PlaidCloud.

1. Copy the SSO URL, Entity ID, and download the Certificate — or
2. Click Copy next to the IDP metadata URL (formatted as https://accounts.google.com/o/saml2/idp?idpid=XXXXXXXXX).

Send this IdP Metadata URL to PlaidCloud support. This is the Entity Descriptor URL that PlaidCloud needs to configure the trust relationship on the identity provider side. Once PlaidCloud receives this URL, the team will complete the Keycloak configuration and notify you when SSO is ready to test.

3. Click Continue to proceed to the Service Provider configuration.

Step 3: Configure Service Provider Details

1. In the ACS URL field, enter the ACS URL provided by PlaidCloud.
2. In the Entity ID field, enter the SP Entity ID provided by PlaidCloud.
3. Leave Start URL blank unless PlaidCloud support instructs otherwise.
4. Set Name ID format to EMAIL.
5. Set Name ID to Basic Information > Primary email.
6. Click Continue.

Step 4: Configure Attribute Mapping

Google Workspace passes user attributes to PlaidCloud in the SAML assertion. At minimum, map the user's email address. If your PlaidCloud configuration uses group-based security role assignments, also map group membership.

Basic Attribute Mapping

Add the following attribute mappings on the Attribute mapping screen:

Click Add mapping to add each row.

Group Membership (Optional)

If you want PlaidCloud to automatically assign users to security groups based on their Google group membership:

1. Click Add mapping.
2. Under Google Directory attributes, select Group membership and choose the relevant Google Groups.
3. Set the App attribute name to groups (confirm the expected name with PlaidCloud support).

Click Finish.

Step 5: Enable the App for Users

By default, a new SAML app is disabled for all users. Enable it for the appropriate organizational units or groups.

1. On the app detail page, click User access.
2. Select the organizational unit or groups that should have SSO access to PlaidCloud.
3. Set the service status to ON.
4. Click Save.

Testing the Integration

After PlaidCloud confirms the configuration is complete:

1. Navigate to your organization's PlaidCloud Workspace (e.g., https://my-workspace.plaid.cloud).
2. You will be redirected to the Google sign-in page.
3. Sign in with your Google Workspace credentials.
4. Upon successful authentication, you will be redirected back to PlaidCloud.

If you encounter errors, verify that:

• The SP Entity ID and ACS URL match exactly what PlaidCloud provided
• The user attempting to log in belongs to an organizational unit or group with the app enabled
• The Name ID format is set to EMAIL and mapped to Primary email
• The IdP Metadata URL you sent to PlaidCloud is accessible

4 - Setting Up Microsoft Entra ID SAML for Single Sign-On

PlaidCloud supports Single Sign-On (SSO) via SAML 2.0. This guide walks through configuring Microsoft Entra ID (formerly Azure Active Directory) as a SAML identity provider so your organization's users can authenticate through Entra when accessing PlaidCloud.

Prerequisites

• An active Microsoft Entra ID (Azure AD) tenant
• An account with one of the following Entra roles: Global Administrator, Cloud Application Administrator, or Application Administrator
• Contact with PlaidCloud support to coordinate the setup and exchange configuration values

Overview

The setup process involves two parties exchanging SAML metadata:

1. You configure an Enterprise Application in Entra ID and provide PlaidCloud with your App Federation Metadata URL.
2. PlaidCloud provides you with the Service Provider (SP) Entity ID and Reply URL (Assertion Consumer Service URL) needed to complete your Entra configuration.

Coordinate with PlaidCloud support to obtain the SP values before completing Step 3 below.

Step 1: Create an Enterprise Application

1. Sign in to the Azure portal and navigate to Microsoft Entra ID.
2. In the left sidebar, select Enterprise Applications.
3. Click + New application.
4. Click + Create your own application.
5. Enter a name for the application (e.g., PlaidCloud SSO).
6. Select Integrate any other application you don't find in the gallery (Non-gallery).
7. Click Create.

Step 2: Enable SAML-Based Single Sign-On

1. After the application is created, select Single sign-on from the left sidebar under Manage.
2. On the "Select a single sign-on method" screen, click SAML.

Step 3: Configure Basic SAML Settings

1. In the Basic SAML Configuration section, click Edit.
2. In the Identifier (Entity ID) field, enter the SP Entity ID provided by PlaidCloud.
3. In the Reply URL (Assertion Consumer Service URL) field, enter the ACS URL provided by PlaidCloud.
4. Click Save.

Step 4: Configure Attributes and Claims

By default, Entra will pass the user's email address and name in the SAML assertion. If your PlaidCloud configuration uses security group assignments from SSO, you should also include group claims.

Add Group Claims

1. In the Attributes & Claims section, click Edit.
2. Click + Add a group claim.
3. Choose Groups assigned to the application (recommended to limit token size).
4. Under Source attribute, select an appropriate value:
   • Group ID — passes the Azure Object ID (UUID) of the group
   • Cloud-only group display names — passes the human-readable group name (for cloud-only groups)
   • sAMAccountName — passes the on-premises group name (for hybrid/synced environments)
5. Click Save.

Step 5: Assign Users and Groups to the Application

Only users and groups assigned to the Enterprise Application will be able to authenticate through this SSO configuration.

1. In the left sidebar, select Users and groups under Manage.
2. Click + Add user/group.
3. Select the users or groups that should have SSO access to PlaidCloud.
4. Click Assign.

Step 6: Retrieve and Send the App Federation Metadata URL

Once the application is configured, locate the Federation Metadata URL and send it to PlaidCloud so the integration can be completed.

1. Navigate to the Single sign-on page for your Enterprise Application.
2. Scroll to the SAML Certificates section.
3. Copy the App Federation Metadata URL.

Send this URL to PlaidCloud support. This is the Entity Descriptor URL that PlaidCloud needs to configure the trust relationship on the identity provider side. Once PlaidCloud receives this URL, the team will complete the Keycloak configuration and notify you when SSO is ready to test.

Testing the Integration

After PlaidCloud confirms the configuration is complete:

1. Navigate to your organization's PlaidCloud Workspace (e.g., https://my-workspace.plaid.cloud).
2. You will be redirected to the Microsoft login page.
3. Sign in with your Entra ID credentials.
4. Upon successful authentication, you will be redirected back to PlaidCloud.

If you encounter errors, verify that:

• The SP Entity ID and Reply URL match exactly what PlaidCloud provided
• The user attempting to log in is assigned to the Enterprise Application
• The App Federation Metadata URL you sent to PlaidCloud is accessible (not blocked by a firewall or conditional access policy)

5 - Setting Up Okta SAML for Single Sign-On

PlaidCloud supports Single Sign-On (SSO) via SAML 2.0. This guide walks through configuring Okta as a SAML identity provider so your organization's users can authenticate through Okta when accessing PlaidCloud.

Prerequisites

• An Okta account with the Administrator role (Super Admin or Org Admin)
• Contact with PlaidCloud support to coordinate the setup and exchange configuration values

Overview

The setup process involves two parties exchanging SAML metadata:

1. You configure a SAML application in Okta and provide PlaidCloud with your Identity Provider Metadata URL.
2. PlaidCloud provides you with the Service Provider (SP) Entity ID and Single Sign-On URL (ACS URL) needed to complete your Okta application configuration.

Coordinate with PlaidCloud support to obtain the SP values before completing Step 3 below.

Step 1: Create a New SAML Application

1. Sign in to the Okta Admin console.
2. In the left sidebar, navigate to Applications > Applications.
3. Click Create App Integration.
4. Select SAML 2.0 as the sign-in method.
5. Click Next.
6. Enter a name for the application (e.g., PlaidCloud SSO) and optionally upload a logo.
7. Click Next.

Step 2: Configure SAML Settings

1. In the Single sign-on URL field, enter the ACS URL provided by PlaidCloud.
2. In the Audience URI (SP Entity ID) field, enter the SP Entity ID provided by PlaidCloud.
3. Leave Default RelayState blank unless PlaidCloud support instructs otherwise.
4. Set Name ID format to EmailAddress.
5. Set Application username to Email.
6. Click Next.

Step 3: Configure Attribute Statements

On the same SAML settings screen, add attribute statements so that PlaidCloud receives user details in the SAML assertion.

User Attributes

In the Attribute Statements section, add the following:

Group Attributes (Optional)

If your PlaidCloud configuration uses group-based security role assignments, add a group attribute statement so group membership is passed in the assertion.

In the Group Attribute Statements section, add the following:

Click Next, then select I'm an Okta customer adding an internal app and click Finish.

Step 4: Retrieve and Send the Identity Provider Metadata URL

Once the application is created, locate the metadata URL and send it to PlaidCloud so the integration can be completed.

1. On the application detail page, select the Sign On tab.
2. Scroll to the SAML 2.0 section and click More details.
3. Copy the Metadata URL (formatted as https://your-org.okta.com/app/your-app-id/sso/saml/metadata).

Send this Metadata URL to PlaidCloud support. This is the Entity Descriptor URL that PlaidCloud needs to configure the trust relationship on the identity provider side. Once PlaidCloud receives this URL, the team will complete the Keycloak configuration and notify you when SSO is ready to test.

Step 5: Assign Users and Groups to the Application

Only users and groups assigned to the application will be able to authenticate through this SSO configuration.

1. On the application detail page, select the Assignments tab.
2. Click Assign and choose either Assign to People or Assign to Groups.
3. Select the users or groups that should have SSO access to PlaidCloud and click Assign.
4. Click Done.

Testing the Integration

After PlaidCloud confirms the configuration is complete:

1. Navigate to your organization's PlaidCloud Workspace (e.g., https://my-workspace.plaid.cloud).
2. You will be redirected to the Okta sign-in page.
3. Sign in with your Okta credentials.
4. Upon successful authentication, you will be redirected back to PlaidCloud.

If you encounter errors, verify that:

• The ACS URL and SP Entity ID match exactly what PlaidCloud provided
• The user attempting to log in is assigned to the application in Okta
• The Name ID format is set to EmailAddress and the application username is set to Email
• The Metadata URL you sent to PlaidCloud is accessible

6 - Manage Organization Administrators

Organizations in PlaidCloud provide a top level area to control options such as single sign-on and member access capabilities. Organizations each contain at least one workspace, which allows workspaces to serve as the main level of tenant separation within PlaidCloud. A workspace helps to align teams with specific areas of interest and isolate access as appropriate. PlaidCloud allows Organizations to have an unlimited number of workspaces.

Managing Organization Administrators

Each Organization in PlaidCloud can assign multiple administrators. Administrators have special privileges to control the Organization. They can do things such as manage billing, update access management, and perform workspace management. To manage administrators:

1. Select the “Organization Settings” menu from the top right of screen
2. Click “Administrators”

This will display the table of current administrators. After the table opens, you may add new administrators, delete existing administrators, or alter administrative privileges.

Adding an Administrator

To add an administrator:

1. Select the “Organization Settings” menu from the top right of screen
2. Click “Administrators”
3. Click the “Add Organization Administrator” button
4. Complete the required fields
5. Click “Add as Administrator”

Deleting an Administrator

To delete an administrator:

1. Select the “Organization Settings” menu from the top right of screen
2. Click “Administrators”
3. Click the delete icon of the desired administrator
4. Confirm and click “Delete as Administrator”

7 - Managing Single Sign-On for Organization

Each Organization can have a custom url (https://plaidcloud.com/sso/<custom_name_here>) for members to access the single sign-on page you specified in the configuration.

To create a custom URL:

1. Select the “Organization Settings” menu from the top right of screen
2. Click “Single Sign-On Security Credentials”
3. Adjust the Single Sign-On URL as desired
4. Click “Update Organization SSO Settings”

Allow Creation of Users Automatically

If Single Sign-On is enabled, you can choose to automatically create members based on successful Single Sign-On authentication. New members will receive the default workspace and security roles specified in the Organization settings. To automatically create members:

1. Select the “Organization Settings” menu from the top right of screen
2. Click “Organization and User Settings”
3. Check the “Create Users Automatically from Single Sign-On” box
4. Choose the desired default workspace

Use of this feature greatly simplifies member management because new members will automatically have access without any additional setup in PlaidCloud. Similarly, if members are removed from the Single Sign-On facility, they will no longer have access to PlaidCloud.

Allow Security Group Assignments from Single Sign-On

If Single Sign-On is enabled, you can choose to pass a group association list along with the positive authentication message. The list’s items will be used to assign a member to the specified groups and remove them from any not specified. This is an effective way to manage security group assignments by using a central user management service such as Active Directory or other LDAP service.

If this option is enabled, security roles will be assigned using the supplied list the next time a member signs in. If the option is disabled, existing members will retain their current security roles until manually updated within PlaidCloud.

8 - Setting Member Expiration Period

If retaining inactive members within PlaidCloud is not desired, members can be set for automatic removal from the Organization after a specified period of inactivity using the expiration capabilities PlaidCloud offers. This automated removal of dormant members can be set as short as one day, if desired.

To set expiration of members:

1. Select the “Organization Settings” menu from the top right of screen
2. Click “Organization and User Settings”
3. Set the desired number of days until expiration
4. Click Update