Akamai will provision a customer’s Production environment when [Configuration and acceptance testing) is complete. This environment is distinct from Development with its own Social Login application(s), Registration application, user data storage, API clients and settings, and flow configurations. Akamai will promote the approved flow(s) and schema(s) from Development to Production, but the following configuration tasks completed for Development must also be completed by the customer for Production:
- Provision new API clients
- Update API client settings
- Configure social providers
- Allow list domains for integration
|janrain.settings.appUrl||Production Social Login application domain|
|janrain.settings.capture.captureServer||Production Registration application domain|
|janrain.settings.capture.appId||Production Registration application ID|
|janrain.settings.capture.clientId||Production Registration API client ID|
|var httpLoadUrl||Production Social Login application load file (http site)|
|var httpsLoadUrl||Production Social Login application load file (https site)|
In addition, if you have a custom domain ) then you will need to replace the rpx_realm API client setting with the rpx_custom_realm setting. These API client settings can usually be found in the Default Settings.
If you are using additional features such as Single Sign-on, you may need to update additional settings. The Akamai Professional Services team supporting your deployment can provide guidance on what is required for your implementation.
Once you have launched your first property using Akamai Registration into production, you may continue to update your Registration experience on the Development environment. Many changes can be released to Production on the customer’s side without assistance from Akamai. However, any changes made to the Registration flow using the Configuration API must be promoted to Production by using the Registration Builder in the Console tool.
Updated over 1 year ago