Setting up SAML SSO
Who can use this feature
- Supported on Team and Enterprise plans
- Note: Team plans are limited to Okta and Google SAML only
- Anyone with an org admin role can access and edit Single sign-on
In this article, we'll show you how to set up single sign-on, so users can authenticate into Writer easily. If you're looking for information about automatically provisioning new users, check out our article, Setting up SCIM provisioning.
What's in this article:
Configuring single sign-on
Start by navigating to the Admin > Single sign-on page.
You'll switch back and forth between Writer and your identity provider (IdP) to share information between the two systems.
Select your IdP (identity provider)
Writer actively supports single sign-on with Okta, Google, and Azure. However, you can also set up single sign-on with other identity providers as well. If you’re using another identity provider, select Other IdPs. Then select Next.
Share information from Writer with your identity provider (IdP)
If you look at Box A, you’ll see 2 fields that you’ll need to paste into your IdP (SP SSO URL and SP Entity ID).
Some IdPs may ask you to upload a metadata XML file from Writer to your IdP. This is rare, but if you need this, select Advanced configuration, then select the download icon to download this XML. You can then upload this into your IdP.
Share information from your identity provider with Writer
Go to the Writer SSO application in your identity provider to retrieve a SAML metadata XML:
Almost all IdPs will provide a SAML metadata XML. This is required from Writer to complete configuration. Once you have the XML from your IdP, upload it in Section B. We’ll analyze this XML and auto-populate the IdP Issuer and IdP SSO URL fields.
Once we have your IdP’s XML uploaded, you can select Done to finish setup.
Single sign-on settings
When you navigate to Admin > Single sign-on, you should see your new SSO identity provider at the top of the page.
To edit your configuration settings, select Edit configuration.
Need to switch identity providers? Select Remove configuration and complete the process with your new identity provider.
Advanced settings
You can also configure several advanced settings for SSO.
Discoverability: Allow uninvited users to create an account via SAML SSO
If enabled, any user whose email address matches one of your domains can join your organization by signing in with SAML SSO. If you enable this option, you'll need to select a default team for these users.
Access for password users: Approval for existing users using password-only sign in
If set to require org admin approval, users will need to be approved by an org admin before joining. If set to allow immediate access, users can join upon request.
Default team: Select which team users join via discoverability
This is the default team users will be added to when joining your organization via domain discoverability.
Allow team members to create passwords and sign in without SSO
If enabled, users from your organization can create their own password and sign in without SAML SSO.
Set up SCIM provisioning
Once your SSO configuration is complete, you can proceed to set up SCIM provisioning for new users. Learn more in our Help Center article Setting up SCIM provisioning.
Frequently asked questions
General
Q: Does your application support SAML 2.0 authentication?
Yes.
Q: Does your application support OIDC authentication?
No.
Q: Does your application provide SAML SP metadata?
Yes, it can be found under advanced configuration on the single sign-on settings page. (Here's a link for admins.) Once you've selected an identity provider, this metadata will be displayed:
Q: What is the SAML Single Sign On URL (ACS URL, Recipient)?
https://app.writer.com/api/access/saml
Q: What is the SAML SP Entity ID (Audience)?
This is found on the single sign-on settings page once an identity provider is selected. For most accounts, this will be app.writer.com though some accounts may see app.writer.com/api/access/saml.
Q: What SAML binding do you support?
HTTP POST
Q: What is the default SAML relay state?
We don't enforce a default value. This can be empty.
Q: What SAML NameID formats do you support?
emailAddress or any other format if the email profile attribute is defined.
Q: What Identity Providers have you previously integrated with successfully?
Azure, GSuite, Okta, OneLogin, PingIdentity.
Q: Can user permissions or roles be assigned based on SAML assertion?
Yes, roles can be modified in the single sign-on settings page.
Q: What additional profile attributes, if any, are you expecting in the assertion/claim from SAML IdP?
first_name, family_name, picture_url
Q: Do you require encrypted assertions?
No.
Q: Do you require encrypted name identifiers?
No.
Q: Do you support Service Provider Initiated SSO, Identity Provider Initiated SSO, or both?
Both.
Q: Do you support "deep linking" and if yes, how do you offer this?
No.
Q: Do you support JIT or OOB user provisioning?
Both.
Q: If OOB user provisioning is required, what methods do you support?
SCIM.
Q: Do you have a non-prod environment we could connect to?
No.
Q: Can the application be configured to remove users who have not logged in for a specific period of time?
No.
Error messages
Q: When I add my email domain and select Next, I’m getting an error that says “One or more of the domains you added are already registered by another organization.”
Q: When I add my IdP metadata XML and select done, I’m getting an error that says “Your IdP configuration failed: Identity provider with same entity id is already registered!”
Q: I got an email from Writer saying that our SSO certificate is about to expire. Where do I upload a new certificate?
Upload a new certificate by navigating to Admin > Single sign-on. Follow the steps listed here.