Self-service account creation

Allow users to self-register without admin approval in self-hosted deployments

Problem

We are running OpenReplay in a corporate environment behind an Identity-Aware Proxy (IAP) / firewall.

Users must already authenticate through the corporate IAP before they can access the OpenReplay instance. However, after successfully passing the corporate authentication layer, users still require an OpenReplay administrator to manually create or approve their OpenReplay account.

This creates an unnecessary additional administrative step, especially in organizations with a large number of internal users.

Current behavior

1. A user accesses the OpenReplay instance through the corporate IAP.
2. The user successfully authenticates with the organization's authentication system.
3. The user cannot create an OpenReplay account directly.
4. An OpenReplay administrator needs to create/provision the user's account and provide access.

Expected behavior

For self-hosted deployments, provide an optional configuration that allows users to create their own OpenReplay accounts after they have successfully authenticated through the organization's external authentication layer.

For example:

1. User accesses OpenReplay through the corporate IAP.
2. User authenticates successfully using the organization's authentication system.
3. OpenReplay provides an option such as "Create Account" / "Sign Up".
4. The user creates their OpenReplay account without requiring manual administrator approval.

Ideally, this should be an administrator-controlled configuration that can be enabled or disabled depending on the organization's security requirements.

Use case

Our OpenReplay installation is accessible only through our corporate IAP/firewall. Therefore, access to the OpenReplay instance is already restricted to authenticated internal employees.

Allowing self-registration would eliminate the need for administrators to manually provision every internal user while still keeping the OpenReplay instance protected behind the organization's authentication layer.

Proposed configuration

Something along the lines of:

ENABLE_SELF_REGISTRATION=true

or an equivalent setting in the OpenReplay administration/configuration UI.

It would also be useful if administrators could disable self-registration when required.

Security consideration

We are not requesting unrestricted public registration.

The OpenReplay instance is already protected by our corporate IAP/firewall, and only users who can authenticate through that layer can reach the OpenReplay application.

The requested feature would simply remove the additional manual account-provisioning step for authenticated internal users.

Summary

Please consider adding an optional self-service account creation / self-registration capability for self-hosted OpenReplay deployments, particularly for installations that already use an external authentication layer such as an IAP, SSO, or corporate proxy.