Account

Configure Cincopa SAML SSO with JumpCloud

Connect JumpCloud to Cincopa with SAML 2.0, then assign the users or groups that should see Cincopa in their application portal.

Prepare the connection

A JumpCloud administrator and a Cincopa account administrator should complete the setup. Open Account Settings → SSO in Cincopa and copy the account's Entity ID and ACS / Reply URL. Check the user identifier and any required claim mappings for the connection.

Use the exact account-specific values. The Cincopa Account Settings guide describes the SSO configuration area.

Configure the JumpCloud application

  • In the JumpCloud Admin Portal, add a Custom SAML application from the SSO applications area.
  • Name it Cincopa so users can recognize it.
  • Import the Cincopa service-provider metadata if available, or enter the Cincopa Entity ID and ACS URL in the corresponding SP fields.
  • Set the SAML subject / NameID to the user identifier expected by the Cincopa connection. JumpCloud defaults to email; verify that the intended user's value matches.
  • Save and activate the application. Obtain the IdP metadata and signing certificate for the connection.

JumpCloud documents its current options in Custom SAML Application Connectors.

Finish setup and test

Import the JumpCloud IdP metadata into Cincopa's SSO settings, or enter the required IdP values and certificate in the available fields. Save the settings, assign a test user or group in JumpCloud, and test the Cincopa application from the user portal.

Keep the application's signing certificate current. If sign-in stops working after a certificate change, compare the active JumpCloud certificate with the one trusted by Cincopa.

User sign-in

Sign in through the JumpCloud URL supplied by your organization and select Cincopa. If the application is absent, contact your administrator to check assignment. If access fails, check the user identifier, ACS URL, Entity ID, and certificate configuration.

See Cincopa's SSO overview for the relationship between the identity provider and Cincopa account access. SSO login does not automatically grant every account permission.