We are working on account management REST API. Some of it's already
available in master and the remaining functionality will come in the next
On Thu, 30 Aug 2018 at 17:47, William Jones <william_jones20(a)outlook.com>
As part of my Keycloak implementation, I would like to offer user self
service, e.g. change password.
I do not wish to theme the built-in user account dashboard, but instead
build the functionality directly into our website.
We are already using the Admin API for user administration, but as I
understand it, it would not be appropriate to use this for actions which
are actually being carried out by the end user. The auditing would be
incorrect, and certain functionality is unavailable anyway - for example,
whilst we could set a new user password via the Admin API, we would have no
way of verifying that the existing user password is correct (we want the
user to provide existing and new, as per the user account dashboard).
As such, is the correct approach to this for us to extend KeyCloak with a
set of custom REST endpoints to be called by an end user rather than an
admin? They will be authenticated at this point so we will be able to pass
down their access token for the authentication.
If so, I assume I should be following the instructions under "Add custom
REST endpoints" detailed at the following URL?
Extending Server | Keycloak Documentation<
This is a very powerful extension, which allows you to deploy your own
REST endpoints to the Keycloak server. It enables all kinds of extensions,
for example the possibility to trigger functionality on the Keycloak
server, which is not available through the default set of built-in Keycloak
keycloak-dev mailing list