Welcome to the Opti ID Beta Program

Thank you for your participation on the Opti ID Beta Program. As part of the testing effort, we WANT you to try and break Opti ID, product switching, and user management within the Admin Center. This page will contain status of all tickets logged as well as feature and functionality updates to be released during beta.

Submitting an Issue

Even if you find something small, please record a ticket. We request that you log these issues through the support team:  https://support.optimizely.com/hc/en-us/requests/new?ticket_form_id=360000000812.

• The ticket type should remain: Question/Incident/Service Request
• Make sure to include: Opti ID Beta in the subject of the ticket.
• Please provide as much information as possible in the ticket to enable the engineering team to reproduce the issue and resolve it. 
• If possible, please provide the steps taken to create the issue and any screenshots.

Issue status log

Feature release timelines

The following listing of features and functionality is expected to release during the beta process. These are estimated timeframes and are subject to change. Prior to each release, a notification will be sent to all beta testers to ensure they are aware of upcoming changes.

May

1. Multi-factor authentication
2. Secondary IDP support
3. Collaboration workflow
4. User invitation workflow
5. Usage consumption and transaction reporting
6. Documentation for automated user migration and role assignment to support GA
7. Change the name of an instance (nickname)
8. View/edit technical contacts 

June -- Opti ID GA!

Installation guide : CMS + Customized Commerce

The beta version of Opti ID is not published to any public NuGet feed, please see the releases below for a downloadable version instead. Each download contains a pre-release version of Opti ID and CMS. Unzip the packages, include them in your solution, update nuget.config to include the directory where you put the packages, and then install the packages in your project file(s).

In startup.cs in the ConfigureServices method, enable Opti ID with following:

services.AddOptimizelyIdentity(useAsDefault: true);

By default, Opti ID is only enabled in shell modules, preview- and edit mode. UseAsDefault enables Opti ID globally throughout the application. AuthenticationOptions can be configured if more control over which authentication scheme should be active when is needed. The namespace EPiServer.OptimizelyIdentity.OptimizelyIdentityDefaults contains constants if you need to reference the scheme while configuring.

You should not call services.AddCmsAspNetIdentity<TUser>() if ASP.NET Identity is not being used.

Run Opti ID locally

You can use Opti ID locally on https://localhost:5000. For this to work you also need some settings. We will provide these to you during the onboarding. These settings are provided automatically when the application is deployed to DXP. You should add these settings in appsettings.json:

  {
  "EPiServer": {
     "Cms": {
        "OptimizelyIdentity": {
           "InstanceId": "xxx",
           "ClientId": "xxx",
           "ClientSecret": "xxx"
           }
        }
     }
  }

Releases : CMS + Customized Commerce pre-releases

For the closed beta we do not publish any packages publicly, instead all necessary packages can be downloaded from here.