Setting up single sign-on (SSO)

If your company uses an identity provider (IdP) like Okta or OneLogin to manage user authentication, you can enable Fastly's single sign-on (SSO) feature to either allow or require your organization's users to sign in to the Fastly web interface using the IdP instead of an email address and password.

Prerequisites

To enable SSO or require that it be applied to all of your organization’s users when they log in to the Fastly web interface, you must:

  • be assigned the role of superuser for your Fastly account
  • have access to your IdP’s administration console

In addition, your IdP must support:

  • Security Assertion Markup Language 2.0 (SAML 2.0)
  • IdP-initiated SSO

You should also review this feature's limitations before enabling SSO.

Enabling SSO

Start by selecting an IdP and configure that provider’s settings keeping in mind the prerequisites. You'll need to retrieve a metadata file containing your IdP's SAML configurations for use in the Fastly web interface:

  1. Log in to the Fastly web interface and click the Account link from the user menu. Your account information appears.
  2. Click the Single sign-on link. The Single sign-on page appears.
  3. Click the Add SAML Configuration button. The Set up single sign-on page appears.
  4. From the menu, select your organization's IdP.

    the sections of the SSO page that allow you to select your identify provider and configure your IdP

  5. Using the configuration details that appear in the Fastly web interface, create a new SAML 2.0 application in your IdP's administration console and assign the application to new and existing users. Refer to your IdP's documentation for more information.
  6. After creating the SAML 2.0 application in your IdP, download the XML metadata file with your application’s SAML configuration. The XML file includes a public certificate used to verify the signature of SAML assertions.
  7. Upload your IdP metadata file. You can do this by dragging and dropping the file into the area provided or by browsing for the file and uploading it.

    the IdP metadata box

  8. Click the Save and Enable SSO button. Your metadata will be saved and the SSO controls will indicate that SSO is enabled.

Requiring SSO for your organization

To require SSO for everyone in your organization except superusers, follow these instructions.

  1. Log in to the Fastly web interface and click the Account link from the user menu. Your account information appears.
  2. Click the Single sign-on link. The Single sign-on page appears.

    the "Single sign-on" control and the "enforce SSO" control on the single sign-on page in the account settings

  3. Select the Immediately enforce SSO checkbox. Currently open non-SSO sessions for users assigned the role of user, billing, or engineer will be logged out and they will need to re-authenticate using SSO via your IdP.

Performing account tasks differently with SSO enabled

If your organization has enabled SSO, you may notice different feature availability in the Fastly web interface. This section describes the differences.

  • Changing your email address and password. Because SSO requires user email addresses in Fastly to match those in the IdP, you won't be able to change your email address while logged in using SSO. You also won't be able to modify your password or enable two-factor authentication.

  • Creating an API token. To create an API token while logged in to the Fastly web interface using SSO, you'll need to reauthenticate with your IdP. Follow the instructions for creating an API token and click the Re-Authenticate button on the Create a Token page.

  • Managing sessions. Sessions created by logging in to the Fastly web interface using SSO expire after 12 hours of inactivity. Sessions created by logging in with a username and password expire after 48 hours.

Changing SSO providers

To change SSO providers, follow these instructions.

  1. Log in to the Fastly web interface and click the Account link from the user menu. Your account information appears.
  2. Click the Single sign-on link. The Single Sign On page appears.
  3. From the Options menu, select Change your SAML configuration. A confirmation message appears.
  4. In the confirmation window, click the Confirm, Disable SSO and Delete button.
  5. Follow the instructions in the enabling SSO section.

Disabling SSO

To disable SSO for your organization, follow these instructions. Disabling SSO won't delete your SSO settings. You can re-enable SSO at any point using the same IdP configuration metadata you uploaded when you first enabled SSO.

  1. Log in to the Fastly web interface and click the Account link from the user menu. Your account information appears.
  2. Click the Single sign-on link. The Single Sign On page appears.

    the "Single sign-on" control and the "enforce SSO" control on the single sign-on page in the account settings

  3. Click the Single sign-on switch to disable SSO for your organization. A confirmation message appears.
  4. In the confirmation window, click the Disable SSO button. SSO will be disabled and will not be required for your organization's users. All active SSO sessions will expire, including your own, and users will automatically be logged out of the Fastly web interface.

Temporarily disabling SSO

If your SSO provider experiences an outage, you may need to temporarily disable SSO for your organization. If you've been assigned the role of superuser, log in using an email address and password, then follow the instructions to disable SSO.

Limitations

Fastly's SSO feature has the following limitations:

  • Users cannot create API tokens from the Fastly web interface when using G Suite SSO for a session's authentication.
  • Fastly does not currently support Service Provider Initiated (SP-initiated) SSO.
  • Fastly does not currently support automatic provisioning and de-provisioning of SSO.
Back to Top