Chapter 13. Deprecated features

The option spi-storage—​ldap—​secure-referral to disable filtering referrals is deprecated. When this feature is removed in a future release, filtering will then be enforced.

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.

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

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.

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.

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.

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.