JumpCloud

Overview

JumpCloud is a cloud directory, identity, and device management platform. Its OpenID Connect SSO application can authenticate Pomerium users through the authorization code flow.

Using JumpCloud as the identity provider gives protected applications one sign-in path. Each application does not need to implement the same external authentication flow. Pomerium can apply route policy from the authenticated identity and request context.

JumpCloud sends authenticated identity data toward Pomerium. Pomerium uses that data with route policy. Pomerium then sends only approved application traffic toward the protected service.

How it works

Create an OpenID Connect SSO application in JumpCloud. Select the issuer and endpoints for the correct US, EU, or India tenant region. Configure the exact Pomerium redirect URI and required email, profile, and group claims.

Configure Pomerium with the exact issuer or provider URL, client ID, and client secret. Use the Pomerium callback URL as an exact redirect URI. Request only the scopes and claims that access policy needs.

Test discovery, signing-key rotation, the authorization code flow, logout, and required claim mappings before production use. Keep provider credentials outside source control.

Example

A team registers Pomerium as an OpenID Connect client in JumpCloud. Users sign in through JumpCloud. Pomerium validates the identity response and applies route policy before it sends an approved request to a private application.

Considerations

• JumpCloud OpenID Connect login is relying-party initiated. Do not depend on an identity-provider-initiated flow.
• Tenant regions use different issuers and endpoints. The configured values must match the tenant.
• JumpCloud remains responsible for authentication, user lifecycle, and the identity data that it issues.
• A standards-based OpenID Connect pattern is not evidence of a vendor-specific connector or partnership.