Use Okta as the SAML 2.0 identity provider for your Cincopa account. An administrator configures the connection and assigns the users who should have access.
Open Account Settings → SSO as a Cincopa administrator. Confirm that SAML SSO is available for the account and copy its Entity ID and ACS / Reply URL. Use the exact values shown for this account, including any connection parameter.
The Account Settings guide explains the Cincopa SSO fields. If those settings are unavailable, contact your account administrator or Cincopa support before configuring Okta.
Okta's SAML field reference explains these fields. Follow any additional claim or signing requirements supplied for your Cincopa connection.
In Cincopa's SSO settings, import the Okta IdP metadata, or enter the IdP values and certificate where your setup requires them. Save the configuration. Assign a test user or group to the Okta application and test sign-in before rolling it out more widely.
This SAML setup uses the identity provider to authenticate the user. It does not require saving a separate Cincopa password in an Okta password-vault app.
Use the organization's Okta URL and select the assigned Cincopa application. If the tile is missing, ask the Okta administrator to check assignment. If the assertion is rejected, compare the ACS URL, Entity ID, certificate, and user identifier on both sides.
Authentication and the user's Cincopa permissions are separate. Review Cincopa SSO and account membership when a user signs in but cannot access the expected content.