Let your team sign in to Hyperping through JumpCloud. You create a custom SSO application in the JumpCloud admin console, copy its metadata URL into Hyperping, and run a test login.
JumpCloud asks for two Hyperping URLs. Both are shown in the setup wizard, and they are the same for every account:
| JumpCloud field | Value |
|---|---|
| SP Entity ID | https://api.hyperping.io/saml/sp |
| ACS URL | https://api.hyperping.io/saml/acs |
Go to MembersAuthentication and click Configure on the JumpCloud card.
The wizard stays open while you work in JumpCloud. Each step below matches a step in the wizard.
In the JumpCloud Admin Console, go to SSO Applications and click + Add New Application, then pick Custom Application.
Check Manage Single Sign-On (SSO) and Configure SSO with SAML, then click Next.
Set the Display Label to "Hyperping" and click Save Application.
Open the application's SSO tab. Set SP Entity ID to https://api.hyperping.io/saml/sp and ACS URL to https://api.hyperping.io/saml/acs. Leave the IdP Entity ID as the value JumpCloud generates, Hyperping reads it automatically from the metadata URL.
Under Sign, select Assertion, and check Declare Redirect Endpoint. Click Save.
Still in the SSO tab, add these user attribute mappings. Note that the JumpCloud attribute names are lowercase:
| Service Provider Attribute Name | JumpCloud Attribute Name |
|---|---|
email | email |
firstName | firstname |
lastName | lastname |
Open the application's User Groups tab, select the groups that should reach Hyperping, and click Save. Users outside these groups get a JumpCloud error before ever reaching Hyperping.

In the SSO tab, find JumpCloud Metadata and click Copy Metadata URL.
In the wizard, paste the URL into Identity provider metadata URL. Hyperping fetches the SSO URL, issuer, and signing certificate from it.
Enter the email domains your teammates use, for example yourcompany.com. Hyperping uses the domain to route login attempts to this connection.
Click Save in JumpCloud once everything is in place.
Back in the wizard, click Test Connection. A popup runs a real login against JumpCloud. Once you see Connection successful, click Complete Setup.
Your provisioning policy is Invite-only and the JumpCloud user has no Hyperping invite yet. Invite them from the Teammates page first, or switch provisioning to Request access or Auto-provision.
The user is not in a group assigned to the application. Check the User Groups tab.
Make sure Sign is set to Assertion in the SSO tab. Hyperping validates the assertion signature against the certificate from your metadata URL.