Bitrix24 SSO Setup via SAML 2.0

We set up SSO (Single Sign-On) for Bitrix24 so your employees can forget about multiple passwords. Imagine: morning, an employee logs into Windows — one password, opens email — another, accesses Jira — a third, then Bitrix24 — a fourth. Passwords are lost, written on sticky notes, and IT spends hours on resets. SSO solves this: one login via a corporate Identity Provider, like Azure AD, Keycloak, or ADFS — and access to all systems. We implement single sign-on turnkey, with guaranteed compatibility and full documentation. Our experience: over 7 years on the market, 80+ successful projects on Bitrix24 and corporate integrations. Request a consultation — we'll assess your project within 1 day and offer the optimal solution.

How SSO for Bitrix24 works

Bitrix24 supports single sign-on via the SAML 2.0 protocol (Security Assertion Markup Language), a standard defined by OASIS. The workflow:

1. User opens Bitrix24.
2. B24 redirects to the Identity Provider (IdP) — Azure AD, Keycloak, ADFS.
3. User authenticates on the IdP (or is already authenticated via Kerberos).
4. IdP returns a SAML assertion — a signed XML document with user data.
5. B24 verifies the signature, extracts attributes, creates or updates the session.

For cloud Bitrix24, SAML SSO is available on Professional and Enterprise tariffs. For on-premise, via the SSO module.

According to 1С-Битрикс documentation, SSO is supported on Professional and Enterprise tariffs.

Configuration on the Identity Provider side

Regardless of the specific IdP, you need to register Bitrix24 as a Service Provider (SP):

Azure AD — register an Enterprise Application, configure SAML, upload Federation Metadata XML. Claim rules: user.mail → NameID, user.displayname → Name, user.department → Department.

Keycloak — create a client with SAML protocol, specify Valid Redirect URIs, configure mappers for attributes. Keycloak is convenient for companies that want to host IdP on their own server.

ADFS — add a Relying Party Trust, configure Claim Issuance Policy. A typical issue: the signing certificate expires — you need to monitor the expiration and update it in B24 settings.

Certificate exchange

SAML relies on trust between SP and IdP, confirmed by certificates:

• IdP certificate — uploaded to Bitrix24 SSO settings. B24 uses it to verify SAML assertions. When the IdP certificate rotates, you must update it in B24, otherwise authorization breaks.
• SP certificate (optional) — if the IdP requires signed AuthnRequest. Generated in B24 settings and uploaded to the IdP.

Recommendation: during IdP certificate rotation, support both old and new certificates for a transition period.

User attribute mapping

The SAML assertion contains user attributes. B24 extracts them and populates the profile:

• NameID (email) → user login in B24
• FirstName / LastName → first and last name
• Department → department (if mapping to B24 structure exists)
• Groups → groups and roles (for automatic permission assignment)

If a user with that email does not exist in B24, they are created automatically on first login (provisioning via SSO). This is configurable: you can allow auto-creation or require prior registration.

Why configure single sign-on?

The average IT department spends up to 4 hours per week on password resets and account support. SSO reduces this time by 90%. Plus, security improves: no passwords transmitted over the network, centralized access policy. Employees don't write passwords on sticky notes, and system access is immediately revoked upon termination. Compare: deploying Keycloak takes 1-2 days, while ADFS requires setting up Windows Server and configuration, which is 2-3 times longer. Azure AD is a compromise if the company already uses Microsoft 365.

What's included

• Audit of current infrastructure and selection of Identity Provider.
• Registration of Bitrix24 as a Service Provider.
• SAML 2.0 configuration on the IdP side.
• Certificate exchange and trust testing.
• Attribute mapping: email, name, department, groups.
• Automatic user provisioning setup.
• Operations documentation and certificate rotation procedure.
• Administrator training.

Process

1. Analysis — we study your infrastructure, select the appropriate IdP.
2. Design — we develop the SSO scheme, agree on mapping.
3. Implementation — we configure the SAML connection, exchange certificates.
4. Testing — we verify authorization, debug errors.
5. Deployment — we hand over documentation, conduct training.

Timeline and cost

Cost is calculated individually, depending on the chosen Identity Provider and required integration depth. Estimated timeline: from 3 to 10 business days. Get an accurate estimate — contact us.

Over 7 years on the market, 80+ successful projects on Bitrix24 and corporate integrations — we guarantee quality and post-deployment support. Reach out for a free consultation — we'll propose a solution tailored to your infrastructure.