I have been informed that it’s now possible to register users via the Web API using the User Account Invitation process and in the process provide a default password such that the registered users don’t have to reply on email?
It is possible, but let me explain it a bit more clearly. There are essentially three ways to do create users.
Allow users to self-register.
Send a user an invite. This allows them to specify their username/password and is considered to be more secure, as the password is never transmitted over insecure means. This method is described in detail in the link which you provided.
Create users with pre-defined username and password. This can be done with XML/JSON through the metadata API. You can follow the example ofhere https://apps.dhis2.org/demo/api/users/oXD88WWSQpR to know how the payload should be structured.
The property “password” should contain the clear-text password of the user, and should be a child of the “userCredentials” node.
Once you create the XML/JSON payload as you like, then you can post this to /api/metaData.
Hope this helps.
Best regards,
Jason
···
On Thu, Jun 25, 2015 at 9:39 AM, Farai Mutero fmutero@gmail.com wrote:
Hi Guys
I have been informed that it’s now possible to register users via the Web API using the User Account Invitation process and in the process provide a default password such that the registered users don’t have to reply on email?
It is possible, but let me explain it a bit more clearly. There are essentially three ways to do create users.
Allow users to self-register.
Send a user an invite. This allows them to specify their username/password and is considered to be more secure, as the password is never transmitted over insecure means. This method is described in detail in the link which you provided.
Create users with pre-defined username and password. This can be done with XML/JSON through the metadata API. You can follow the example ofhere https://apps.dhis2.org/demo/api/users/oXD88WWSQpR to know how the payload should be structured.
The property “password” should contain the clear-text password of the user, and should be a child of the “userCredentials” node.
Once you create the XML/JSON payload as you like, then you can post this to /api/metaData.
Hope this helps.
Best regards,
Jason
–
On Thu, Jun 25, 2015 at 9:39 AM, Farai Mutero fmutero@gmail.com wrote:
Hi Guys
I have been informed that it’s now possible to register users via the Web API using the User Account Invitation process and in the process provide a default password such that the registered users don’t have to reply on email?