You can roll back OpenEdge Command Center to local authentication if the external identity provider (IdP) is unavailable, misconfigured, or prevents users from signing in. This rollback applies to the entire OpenEdge Command Center deployment. In a multiple-node deployment, the rollback and restart must be completed on all servers. Individual users cannot switch authentication modes for themselves.

The IdP configuration is not deleted during the rollback. It remains stored and inactive, allowing you to reactivate the IdP authentication later, without entering the configuration values again.

Prerequisites

Before you begin, ensure that the following conditions are met:

  • You can sign into the OpenEdge Command Center server host with root privileges on Linux, or with Administrator privileges on Windows.
  • You can restart the OpenEdge Command Center server and all other servers in a multiple-node deployment.

To restore local authentication, perform the following steps:

  1. On the OpenEdge Command Center server host, run SWITCHAUTHMODE --LIST to confirm the exact name of the local configuration.
  2. To activate local authentication, run SWITCHAUTHMODE --ACTIVATE LOCAL on the OpenEdge Command Center server host.

    This utility sets the local configuration as the active configuration and keeps the IdP configuration stored and inactive.

  3. Restart the OpenEdge Command Center server:
    oeccserver stop
oeccserver start

    In a multiple-node deployment, restart every node because each node reads the active configuration at startup.

  4. Open the OpenEdge Command Center URL and sign in as a restored local user by entering user name and password.

    The login page displays the Username and Password fields, instead of the Sign in with OAuth button of the IdP.

  5. To reset the password, click Forgot password.
  6. Run SWITCHAUTHMODE --LIST and confirm that the IdP configuration is still stored and is now inactive. You can activate it later without entering its values again.