Glyue User Docs
  • What is Glyue?
  • Tutorials
    • Start Here
    • Building a Single-Step Integration
      • 1. Creating the Integration
      • 2. Calling the External System
      • 3. Running the Integration
      • 4. Crafting the Output
    • Building a Multi-System Integration
      • 1. Connecting to the Core
      • 2. Field Mapping
      • 3. Running the Integration
    • Building an Event-Driven Integration
      • 1. Setting up the Mock CRM
      • 2. Receiving Inbound Requests
      • 3. Triggering the Integration from the CRM
    • Building an Email Integration
      • 1. Create and Configure the Integration
      • 2. Input Validation
      • 3. Get Story IDs from Hacker News
      • 4. Get Story Content
      • 5. Sending the Email
      • 6. Wrapping Up
      • 7. Extra credit
        • extra_credit.json
    • Building a RESTful CRUD Web Service
      • 1. Integration Setup
      • 2. Vault Setup
      • 3. Create Web Service Endpoints
      • 4. Execute Web Service Endpoints with Vault Methods
      • 5. Vault Code Examples and Explanation
    • Building a Retrieval API against FIS CodeConnect
      • 1. Integration Setup
      • 2. Service Request Setup
      • 3. Field Mapping Setup
      • 4. Integration and Service Request Hook Setup
      • 5. Testing the Integration
      • 6. Common Errors
    • What is Pre-Mapping?
      • Before you start
      • Bookmarks
      • Source and Targets
      • Field Mapping Status
      • Field Mapping Comments
      • Summary
  • How-To Guides
    • How to Run an Integration from Glyue
    • How to Invite New Users
    • How to Create a Value Mapping Set
    • How to Build and Deploy a Custom Frontend
    • How to Migrate an Integration
    • How to Set Up Single Sign On (SSO)
      • Glyue Setup
      • JumpCloud Setup
      • Azure Setup
      • Okta Setup
      • Glyue SAML Config Reference
    • How to Install the Glyue App for Zoom Contact Center
    • How to use the Vault
  • Reference
    • Integration Builder Page
    • Integration Anatomy
    • Integration Components
      • Integration
      • Service Request
      • Field Mapping
      • Value Mapping Set
      • Value Mapping
      • Validation Rule
      • Mask
      • Integration Config
      • Integration Engine Versions
    • Integration Lifecycle
    • Special Functions
      • add_run_label
      • callint
      • debug
      • end
      • get_namespace
      • humanize
      • import_helper
      • keep
      • list_files
      • map_value
      • open_glyuefile
      • open_vault
      • Data Manipulation Utilities
      • calladapter
    • Special Variables
      • __adapter_config__
      • input
      • parentint
      • retvalue
      • run_history_id
      • Iterables
        • fitem/fidx
        • sritem/sridx
        • vritem/vridx/vrmsg
    • Adapters
      • Generic HTTP Adapter
      • Email SMTP Adapter
    • Web Service Endpoints
    • Vault Reference
  • Glyue Platform Reference
    • Banking Core Connectivity Guide
    • Authentication
    • Permissions
      • Service Accounts
      • Organizations
    • Frontends
    • Idempotency Layer
    • Integration Scheduler
    • Governance Reports
    • Arbitrary Integration Request Content Support
    • Admin Components
    • Logging
  • ETL
    • Glyue ETL Overview
    • Data Connectors
    • Workflows
    • Run History
    • Scheduler
Powered by GitBook
On this page
  • Create the Glyue SSO Application in JumpCloud
  • Provide Glyue’s SAML Metadata to JumpCloud
  • Add Users
  • Activate the SSO App

Was this helpful?

  1. How-To Guides
  2. How to Set Up Single Sign On (SSO)

JumpCloud Setup

PreviousGlyue SetupNextAzure Setup

Last updated 1 year ago

Was this helpful?

Before continuing, this user should be a JumpCloud admin for the organization, and a SAML Config must be created in the Glyue Environment.

Create the Glyue SSO Application in JumpCloud

From the JumpCloud dashboard, select SSO from the left-hand navbar and click the Add New Application button.

At the bottom of the page, click the Custom SAML App button.

Provide a Display Label. We recommend something like Glyue DEV, Glyue PROD, etc. Provide a Description if desired.

Provide Glyue’s SAML Metadata to JumpCloud

Click the SSO tab.

The Glyue environment SAML metadata will be required for the next step.

Glyue always serves its metadata at https://[domain]/sso/saml2/metadata/. If this user is also a Glyue administrator, the metadata URL will be displayed on the Admin site under SAML Configs.

Click the Upload Metadata button and upload the metadata provided by Glyue.

Provide a custom IdP Entity ID. Any unique value will do.

Add Users

On the User Groups tab users/groups can be assigned to the application. Only assigned users/groups will be able to authenticate with Glyue via JumpCloud.

Add the desired users/groups for the organization. This can also be done later.

Activate the SSO App

Click Activate at the bottom of the screen.

Back in Configured Applications, select the new SSO App and click Export Metadata.

An XML file should be downloaded. This file will be needed on the Glyue side in order to add JumpCloud as an IdP, which is the last step. If not a Glyue admin, please provide this file to a Sandbox Banking employee.

Lastly…

Don’t forget to assign users or groups to the new application- otherwise they won’t be able to authenticate with Glyue via SSO.