Quip supports SAML (Security Assertion Markup Language) SSO through Microsoft Active Directory Federation Services (ADFS) and Ping Federate as identity providers (IdPs). With this configuration, users log in to Quip using their corporate ADFS or Ping Federate credentials rather than a separate Quip password. This article provides configuration steps and answers to frequently asked questions about Quip SSO with these identity providers.
This article explains how to configure Microsoft Active Directory Federation Services (ADFS) or Ping Federate as a SAML identity provider for Quip single sign-on (SSO). It lists the requirements, the configuration steps, and answers to common questions. Before you start, review the guide Quip SAML Single Sign-On (SSO) Setup Overview for additional information on the process, as well as recommended guidelines.
Once you are done testing your SAML setup, select the dropdown on your configuration within the Quip Admin Console and select "Manage". Then select "Enable for Entire Company" and save to apply the configuration to all of your users. All of your users are then directed to log in with their corresponding Identity Provider credentials.
If uploading the metadata file within your Quip configuration does not work, you can manually paste the configuration into a textbox by selecting 'Configure manually'.
The Quip SAML configuration allows users to complete either an Identity Provider (IdP) Initiated Flow or a Service Provider (SP) Initiated Flow.
If you are using the Test User option in the Quip SAML configuration, you will see an error when using an IdP-initiated flow, because the configuration is not fully enabled.
Admins cannot configure more than one Identity Provider to one Quip site.
If you need to update your existing SAML configuration certificate, follow the guide How to Add/Update a New SAML Certificate for Quip.
000390281

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.