Skip to main content

Guide

Connect your company domain to Kopexa: Set up SSO securely

Verify your domain, exchange SAML metadata and test sign-in, with important distinctions between auto-join, MFA and Space access.

Connect your company domain to Kopexa: Set up SSO securely
Julian Köhn
|Read time: 3 minutes

SSO moves authentication to your identity provider. Assigning the Kopexa application there becomes an important operational task. Prepare the transition before enabling it for the entire domain.

This workflow runs from domain verification to sign-in testing. At the end, separately check authentication, organisation membership and Space access for intended users.

What you need

You need access to Kopexa organisation settings, DNS management for your email domain and your identity provider’s SAML configuration. These are organisation domains used for sign-in, rather than internet domains technically assessed within a Space.

Identify existing users of the domain beforehand. After activation, every user of this domain must sign in through the identity provider; their previous password sign-in is no longer available.

Verify the domain

Open Settings → Domains in the organisation and add your domain. Copy the displayed DNS TXT record into your DNS provider. Once publicly resolvable, request verification again.

Use exactly the value Kopexa displays. A domain confirmation from another service will not work. SSO can be configured only for a verified domain.

Exchange metadata

The identity provider needs Kopexa metadata at https://id.kopexa.com/sso/saml/metadata. The reply URL is https://id.kopexa.com/sso/saml/acs. Ensure the provider sends the user’s email address.

In Kopexa, open the domain’s SSO settings and enter the provider’s metadata URL or XML. The signing certificate is taken from it. The URL is loaded when metadata is imported; explicitly plan later certificate changes.

The Kopexa documentation describes all fields.

Check before switching

Assign the application to everyone who needs it in the provider. Enforce MFA there: SSO replaces Kopexa’s additional two-factor prompt. Agree a recovery procedure for a faulty configuration too.

Enable SSO during the agreed change window. Then test with an existing user and an intended new user. Also test rejection of an unassigned account.

Auto-join does not grant Space access

Auto-join adds users of the domain as organisation members when they sign in through SSO. Without it, an organisation invitation is still required. Space visibility remains separately controlled.

Record this decision in your access control policy. When someone leaves, assess active sessions and access according to your procedure; blocking sign-in alone does not justify an unverified claim about every existing session.

Accept the transition as an access change

A successful administrator login is insufficient. Before the change window, record affected user groups and who confirms testing. Existing employees, new members and explicitly unauthorised accounts need different expected outcomes.

Distinguish four layers: domain ownership, successful SAML authentication, organisation membership and Space access. If sign-in works but a Space is missing, repeating DNS verification will not help. If SAML sign-in itself fails, the Space role is not yet the cause.

Record errors with their time and affected layer. SAML responses can contain personal information; do not paste them unfiltered into public tickets. Initial support coordination often needs only symptoms and timing.

Suitable completion evidence includes verified configuration and results for the intended account types. Passwords, private keys and complete tokens do not belong in it.

Take over ongoing operation

Name owners for certificates, application assignments and errors. Document a successful test as evidence for the measure and set the next review trigger. This keeps the evidence history useful after setup.

Quick answers

Frequently Asked Questions

Still have a question? Find the answers here.

Does auto-join automatically give everyone access to every Space?

No. Auto-join concerns organisation membership during SSO sign-in. Space permissions are assigned separately.

Sources

  1. Organisation domains and SAML SSO — Kopexa [Accessed ]