Seems like a nice addition at the first place. But the more I think about this feature, the more questions arise. Maybe the most important one: Which attributes of the user really belong to Keycloak? My answer would be: Only those few which are necessary for IAM. All other attributes, I would argue, belong to the business model, somewhere outside the IAM system.
Can you show how to redirect to change password after temporary password was placed in login form , but ussing users federation with postgres or mariadb
Hi Niko, thanks for your useful videos about KeyCloak.
Seems like a nice addition at the first place. But the more I think about this feature, the more questions arise. Maybe the most important one: Which attributes of the user really belong to Keycloak? My answer would be: Only those few which are necessary for IAM. All other attributes, I would argue, belong to the business model, somewhere outside the IAM system.
Can you show how to redirect to change password after temporary password was placed in login form , but ussing users federation with postgres or mariadb