Chapter 6. Deprecated features


In previous sections, some features have already been mentioned as deprecated. The following sections provide details on other deprecated features.

6.1. Default db option for production

In previous releases, the db option defaulted to dev-file both in production (start) and development (start-dev) modes while dev-file has never been supported in the production mode. In this release, we have deprecated this behavior and in some future release the db option will not default to dev-file in production mode. For build or non-optimized start and non-server commands import, export, or bootstrap-admin in the production profile, a value should be explicitly supplied.

This change is to prevent the unintentional usage of the dev-file (H2) database in a production environment, which is typically indicative of a misconfiguration.

6.2. APIs for JavaScript Authorization client

The following APIs for the JavaScript Authorization client are deprecated and will be removed in the next major release:

  • The ready property on the KeycloakAuthorization instance.
  • The init() method on the KeycloakAuthorization instance.

These APIs are no longer needed as initialization is done automatically on demand when calling methods on the KeycloakAuthorization instance. You can safely remove any code that depends on these APIs.

6.3. Endpoint for initiate registration from OIDC client

The /realms/<realm>/protocol/openid-connect/registrations endpoint, which was used for initiating registration by OIDC client, is now deprecated because a standard way exists to initiate registration from the OIDC client. This way is now supported by Red Hat build of Keycloak. It uses the parameter prompt=create.

6.4. getAll() methods in Organizations and OrganizationMembers APIs

getAll() methods in Organizations and OrganizationMembers APIs are now deprecated and will be removed in the next major release. Instead, use corresponding list(first, max) methods in Organizations and OrganizationMembers APIs.

6.5. Transport stacks for distributed caches

The udp, jdbc-ping-udp, tcp, azure, ec2 and google transport stacks have been deprecated. Users should use the TCP based jdbc-ping stack as a direct replacement.

Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat