Permalink
Fetching contributors…
Cannot retrieve contributors at this time
71 lines (46 sloc) 3.1 KB

It is important that you upgrade {project_name} server first, and then upgrade the adapters. Earlier versions of the adapter might work with later versions of {project_name} server, but earlier versions of {project_name} server might not work with later versions of the adapter.

Compatibility with older adapters

As mentioned above, we try to support newer release versions of {project_name} server working with older release versions of the adapters. However, in some cases we need to include fixes on the {project_name} server side which may break compatibility with older versions of the adapters. For example, when we implement new aspects of the OpenID Connect specification, which older client adapter versions were not aware of.

In those cases, we added Compatibility modes. For OpenId Connect clients, there is a section named OpenID Connect Compatibility Modes in the {project_name} admin console, on the page with client details. Here, you can disable some new aspects of the {project_name} server to preserve compatibility with older client adapters. More details are available in the tool tips of individual switches.

Upgrading the EAP Adapter

Upgrading the JavaScript Adapter

To upgrade a JavaScript adapter that has been copied to your web application, complete the following steps:

  1. Download the new adapter archive.

  2. Overwrite the keycloak.js file in your application with the keycloak.js file from the downloaded archive.

Upgrading the Node.js Adapter

To upgrade a Node.js adapter that has been copied to your web application, complete the following steps:

  1. Download the new adapter archive.

  2. Remove the existing Node.js adapter directory

  3. Unzip the updated file into its place

  4. Change the dependency for keycloak-connect in the package.json of your application