Custom Authentication and Registration Module for 1C-Bitrix

We are a team with over 10 years of experience in Bitrix development, having completed more than 50 projects on authentication customization. We often encounter requests that go beyond the standard bitrix:system.auth.form component. Business requires phone number authentication with OTP, login via Gosuslugi (ESIA), two-factor authentication, single sign-on for multiple sites (SSO), custom registration fields with verification. The cost of developing an authentication module depends on the feature set, but you can always get a free project assessment. We implement the module in 1–10 weeks. Want to know more? Contact us for a consultation.

Why the Standard Authentication Component Is Insufficient

The standard component handles basic tasks but does not support OTP authentication, ESIA integration, flexible 2FA, or SSO. Real projects need custom scenarios: legal entity registration with INN verification, soft social network binding, login attempt quotas. Developing your own module gives full control over logic and security. Savings on license fees when using a custom module can reach 50% per year.

How Authentication Works in Bitrix

Bitrix provides several extension points for the authentication system. One-time password (OTP) is a key mechanism for phone number confirmation.

Social authentication is implemented via the socialservices module. Providers are extended through a class inheriting \Bitrix\SocialServices\Base. For non-standard providers (Telegram, Gosuslugi), a custom class is created. See Bitrix documentation on social services for details.

Token/API-key authentication — via the OnBeforeUserLogin event handler or middleware in OnPageStart.

Event model: key events for extending authentication:

• OnBeforeUserLogin — before login (can block)
• OnAfterUserLogin — after successful login
• OnUserLoginAttempt — for each attempt (logging, rate limiting)
• OnBeforeUserRegister — before registration
• OnAfterUserRegister — after successful registration

How to Implement Phone Number Authentication with OTP

The most common request. Workflow:

1. User enters phone number.
2. Server generates OTP code (6 digits), saves in session or cache with TTL 5 minutes.
3. Sends SMS via provider (SBOL, Infobip, SMS.ru).
4. User enters code.
5. Server verifies code, finds user by field UF_PHONE or PERSONAL_PHONE, logs in via CUser::Authorize($userId).

// OTP verification and authorization
public function verifyOtp(string $phone, string $code): bool
{
    $session = Application::getInstance()->getSession();
    $stored = $session->get('otp_' . md5($phone));

    if (!$stored || $stored['code'] !== $code || $stored['expires'] < time()) {
        return false;
    }

    $session->delete('otp_' . md5($phone));

    // Find user by phone
    $user = UserTable::getRow([
        'filter' => ['=PERSONAL_PHONE' => $phone, '=ACTIVE' => 'Y'],
        'select' => ['ID'],
    ]);

    if ($user) {
        CUser::Authorize($user['ID']);
        return true;
    }

    // Auto-register if needed
    return $this->autoRegister($phone);
}

Integration with Gosuslugi (ESIA)

Authentication via Gosuslugi uses ESIA (Unified Identification and Authentication System) with OAuth 2.0 + OpenID Connect protocol. Features:

• Requires registration of the information system in the Ministry of Digital Development registry.
• Requires PKCS#7/GOST-R signature of requests (Cryptopro or OpenSSL with Russian algorithms).
• ESIA test environment is available at a separate URL.

The integration is implemented as an authentication provider inheriting \Bitrix\SocialServices\Base or as a separate handler with redirect URI.

Single Sign-On (SSO) for Multiple Sites

In a multisite configuration, Bitrix supports SSO through the "Session Storage" mechanism. For sites on different domains, it is implemented via:

• Common second-level domain (.example.ru) with cookies on that domain.
• OAuth2 server on the main site + clients on child sites.
• JWT tokens in URL parameters for cross-domain transition.

Two-Factor Authentication (2FA)

Time-based One-time Password (TOTP) — standard algorithm compatible with Google Authenticator, Yandex.Key. 2FA is implemented via the OnAfterUserLogin handler:

public static function onAfterUserLogin(array &$params): void
{
    $userId = $params['USER_ID'];

    if (self::is2FAEnabled($userId)) {
        // Save flag "2FA required" in session
        $session = Application::getInstance()->getSession();
        $session->set('2fa_required', true);
        $session->set('2fa_user_id', $userId);

        // Log out current session and redirect to code input page
        CUser::Logout();
        LocalRedirect('/auth/2fa/');
    }
}

Custom Registration Fields

Registration form fields are extended via user fields UF_* of the user module. Specific tasks:

• INN/OGRN verification for legal entity registration — via the Federal Tax Service API or dadata.ru.
• Email confirmation via unique link — standard Bitrix mechanism plus email customization.
• Document upload during registration — via UF_ fields of file type with moderation.

Authentication Method Comparison

Custom OTP authentication reduces server load by 3 times compared to constant redirection to external services. A custom module is 2–3 times faster for specific scenarios than the standard solution.

Typical Development Timelines

The module is tested for compliance with security requirements: brute force protection (rate limiting), CSRF protection, proper session termination, token storage in hashed form.

What You Get as a Result

• A fully functional authentication and registration module ready for use.
• Commented source code.
• Installation and configuration documentation.
• Administrator instructions for the site.
• 30-day support guarantee from the date of delivery.

Contact us for a project assessment — we will offer the optimal solution for your tasks. Request the development of an authentication module and get a consultation.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.