Update Keycloak to the latest version.
We know this will break our current login and registration templates, and therefore we need to either:
- Create new templates from scratch; or
- Implement both forms directly in the application and integrate them with the Keycloak API.
The first option is preferred, but it raises the question of how future-proof this approach is, given that the template formats have changed frequently.
The latest version of Keycloak includes OAuth 2.1 support, which allows us to use the new security features PAR and DPoP. We aim to implement PAR in this issue and look at DPoP later.
Update Keycloak to the latest version.
We know this will break our current login and registration templates, and therefore we need to either:
The first option is preferred, but it raises the question of how future-proof this approach is, given that the template formats have changed frequently.
The latest version of Keycloak includes OAuth 2.1 support, which allows us to use the new security features PAR and DPoP. We aim to implement PAR in this issue and look at DPoP later.