Skip to main content

Configuration Deployment

Overview

Configuration Deployment allows seamless cloning and transferring of settings between LoginRadius tenants, ensuring efficient integration management. With automated workflows, version control, and rollback options, it maintains consistency, security, and scalability while minimizing errors. Whether deployed manually or automatically, it simplifies updates across environments without disruption.

Key Features

The Configuration Deployment Tool ensures smooth synchronization and management of settings across multiple environments while maintaining flexibility and control. The key features include

  • Seamless Environment Management – Sync configurations effortlessly across development, staging, and production environments.
  • Selective Syncing – Transfer specific configurations or features, allowing granular control over deployments.
  • JSON Preview: View a detailed JSON summary of the configurations to be deployed for transparency and accuracy.
  • Risk-Free Testing – Validate updates in a sandbox environment before applying them to production.

Ideal for businesses managing multiple LoginRadius tenants, this tool ensures smooth updates, minimal downtime, and secure configuration handling. For details on LoginRadius tenants, refer to this documentation.

Configurations

The Configuration Deployment tool is available under Admin Console > Tenant Settings > Configuration Deploy. Here, you can quickly transfer settings using the Configuration Deployment tool, ensuring consistency across environments. Kindly refer to the detailed steps below for Configuration Deployment.

  • Navigate to the Tenant Settings > Configuration Deployment section in the LoginRadius Admin Console.
  • Select the Source Site
    • From the Source Site dropdown, select the site containing the configurations you want to transfer.
  • Select the Destination Site
    • From the Destination Site dropdown, choose the target site where the configurations will be deployed.
    • Click on deploy configuration.

Below, you’ll find detailed descriptions of transferable configurations and their associated sections in the Admin Console.

Transferable Configurations

Basic Configuration

This section includes fundamental settings such as session management and password policies.

SettingLocation
Remember MeSecurity > Session Management
Access RestrictionsSecurity > Attack-protection > Domain-access-management
Password HistorySecurity > Password Policy
Token LifetimeSecurity > Session Management

Email Workflow

Transfer email-related configurations, including SMTP, templates, and request control settings.

SettingLocation
Email FlowAuthentication > Authentication Configuration
Email SMTP ConfigurationBranding > Email-sms-provider
Email TemplatesBranding > Email Templates
Email Request Control SettingsBranding > Email Templates

SMS Workflow

Sync SMS-related configurations, such as templates, provider settings, and request controls.

SettingLocation
SMS TemplatesBranding > Email-sms-provider
SMS Provider ConfigurationBranding > SMS Templates
SMS Request Control SettingsBranding > SMS Templates

Features

This section includes configurations related to integrations and cloud connector settings.

SettingLocation
FeaturesIntegrations > SSO Integrations
IntegrationsIntegrations > SSO Integrations

📌 Note: Avoid selecting the Integration option unless you know its impact. Contact LoginRadius Support for guidance.

Password Encryption Settings

Manage password encryption and hashing algorithms.

SettingLocation
Password ExpirationSecurity > Password Policy

Registration Form Schema

Sync the standard and custom field settings for registration forms.

SettingLocation
Traditional Form SchemaBranding > Forms

Custom Object(s)

Transfer custom object settings, such as name, ID, and size. Please note that the stored data will not be transferred.

SettingLocation
Custom ObjectBranding > Forms > Custom Objects

Security Questions

Sync customized security questions.

SettingLocation
Security QuestionsSecurity > Security Questions

Multi-Factor Authentication

Transfer multi-factor authentication settings, including SMS templates.

SettingLocation
Multi-Factor AuthenticationSecurity > Multi-Factor Authentication
SMS PasscodeSecurity > Multi-Factor Authentication

Hosted Pages

All Hosted Pages settings will be transferred from the source site to the destination site during configuration deployment.

📌 Note: If a Hosted Pages file (e.g., before.js) is updated or uploaded with the same file name in the development environment, it will also update in the production environment after deployment because both environments share the same file link.

Recommendation: To avoid unintended updates in production, upload files with unique names (e.g., before-rev1.js or before-rev2.js) when making changes in development. A new file name ensures the changes stay isolated and take effect immediately without affecting the production environment.

Non-Transferable Configurations

The following configurations cannot be transferred due to dependencies or limitations.

FeatureExamples
Social ProvidersOAuth Provider, ADFS Provider, SAML Provider
Data ComplianceGDPR Compliance, Encryption in Transit
API SettingsAccount API Keys, Additional API Secret
SDK and LibrariesMobile Library, Turnkey Plugins
Customer ManagementCustomer Segmentation, Insights
Security FeaturesCaptcha Settings, IP Access Restrictions
Theme CustomizationHosted Pages Themes, Voice OTP

For more details, you may contact LoginRadius Support.

Best Practices

  • Use a Staging Environment: Test configurations in a staging environment before deploying to production to avoid impacting live systems.

  • Review Configurations: Verify selected settings in the "Configuration to be deployed" section for accuracy before deployment.

  • Backup Current Configurations: Create a backup of the destination site’s existing configurations in some other environment to perform rollbacks if needed.

  • Deploy Incrementally: Deploy configurations feature by feature to identify and resolve issues easily.

  • Monitor Post-Deployment: Validate the deployed settings and monitor the destination site for errors or anomalies.

  • Secure Access: Restrict access to configuration deployment tools to authorized personnel only.