[Notification] We're upgrading the JumpCloud Support Center the week of September 30th.

Support Center

Single Sign On (SSO) with Twilio

Important: This article contains out-of-date information. For current application information, see Connecting Applications with JumpCloud Using Pre-Built Connectors.



Configure the JumpCloud SSO Application

  1. Access the JumpCloud Administrator Console at https://console.jumpcloud.com.
  2. Select Applications in the main navigation panel.
  3. Select the + in the upper left, scroll or search for the application in the 'Configure New Application' side panel, then select 'configure'.
  4. Optionally, enter Twilio for the Display Label. This label will appear under the Service Provider logo within the JumpCloud User Portal.
  5. You can upload a service provider application's XML metadata file to populate SAML connector attributes for that application. The attributes populated by the metadata file may vary by the application. To apply a metadata file for the application you're connecting, click Upload Metadata. Navigate to the file you want to upload, then click Open. You'll see a confirmation of a successful upload. Be aware that if you upload more than one metadata file, you'll overwrite the attribute values applied in the previously uploaded file.
  6. In the IDP Entity ID field, enter https://YOURDOMAIN.TLD (e.g., https://thebestwidgets.com).
  7. Select Upload IdP Private Key and upload the private.pem file generated according to the above prerequisites.
  8. Select Upload IdP Certificate and upload the cert.pem file generated according to the above prerequisites.
  9. In the SP Entity ID field, enter https://preview.twilio.com/iam/Accounts/Your_Account_SID/saml2. You can get your account SID from the Twilio Admin Console.
  10. In the ACS URL field, enter https://preview.twilio.com/iam/Accounts/Your_Account_SID/saml2.
  11. Select the Include Group Attribute check box to include the groups a user is a member of in SAML assertions. When this field is selected, all groups that connect the user to the application are included in assertions to that application. The Groups Attribute Name is the service provider's name of the group attribute. By default, the attribute name is memberOf.
  12. In the Groups Attribute Name field, enter roles.
  13. In the Default RelayState: field, enter the name of your flex runtime domain. You can find it here: https://www.twilio.com/console/runtime/overview. If not leave it blank
  14. Select the Declare Redirect Endpoint check box. Clear this check box if your Service Provider doesn't need to include a redirect endpoint.
  15. In the field terminating the IdP URL, either leave the default value or enter a plaintext string unique to this connector.
  16. Select Activate.

Configure the Service Provider

  1. Go to Configure SSO in Twilio Console: https://www.twilio.com/console/flex/users/single-sign-on
  2. Enter the following values:
  • Friendly Name: Enter JumpCloud.
  • x.509 Certificate: Open the .pem file from the JumpCloud Admin Console in your favorite text editor and copy/paste the entire contents of the file, including all dashes.
  • Identity Provider Issuer: Enter your Identity Provider Entity ID (https://jumpcloud.com).
  • Single Sign-On URL: Enter your IdP URL from the JumpCloud Admin Console.
  • Default Redirect URL: Optionally include this field. You can find its value here: https://www.twilio.com/console/runtime/overview. Otherwise, leave it blank.
  1. Click Save.

Validate SSO authentication workflows

IdP Initiated

  • Access the JumpCloud User Console at https://console.jumpcloud.com.
  • Select the Service Provider icon.
  • This should automatically launch and login to the application.

SP Initiated

  • Navigate to your Service Provider application URL.
  • You will be redirected to log in to the JumpCloud User Portal.
  • The browser will be redirected back to the application and be automatically logged in.

Last Updated: Aug 20, 2019 10:03AM MDT

Related Articles
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found