We do, either through import at startup for a new realm or partial import
at runtime. However, those are bulk operations to import a bunch of stuff
at the same time. We already let the admin set the credentials as well as
role-mappings, but it has to be done with several calls. I can see a few
valid uses cases to be able to add users:
* Some sort of scripted migration of users, where you want to import one
user at a time and you have access to the hashed password
* An external user provisioning system and/or user self-registration service
On 12 June 2017 at 13:50, Bill Burke <bburke(a)redhat.com> wrote:
don't we already support this via import?
On 6/12/17 3:05 AM, Stian Thorgersen wrote:
Not always. What about for instance the case when folks are importing a
bunch of users and have a dB filled with hashed passwords.
On 10 Jun 2017 6:09 am, "Bill Burke" <bburke(a)redhat.com> wrote:
> credentials is somethign that is supposed to be set by the user.
>
>
> On 6/9/17 5:49 AM, Stian Thorgersen wrote:
> > Currently the admin endpoints ignores credentials when creating the user
> > and a second post is needed to add credentials.
> >
> > I don't see any reason why it has to be this way and we should be able
> to
> > change it?
> >
> > We already have a PR for it
https://issues.jboss.org/brows
> e/KEYCLOAK-5026.
> > _______________________________________________
> > keycloak-dev mailing list
> > keycloak-dev(a)lists.jboss.org
> >
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>