Hi all,
taking up this thread, there has been any progress with version 2.19?
I have been trying all the combinations suggested here in version
2.19, but with no success.
Thank you!
On 17 February 2015 at 16:56, Jose Garcia Muñoz josem...@gmail.com wrote:
Sorry guys but do you have any news
Sorry guys but do you have any news from your end? It will be useful to
know if the problem is because something that I m not doing properly or due
to some bug in the backend...
Thank you!
On Sun, Feb 15, 2015 at 2:04 PM, Jose Garcia Muñoz josem...@gmail.com
wrote:
Thank you Morten,
Now I
Thank you Morten,
Now I called the Sierra Leone API as follows
curl.exe -d @user.json https://apps.dhis2.org/demo/api/users/OYLGMiazHtW -H
Content-Type:application/json -u admin:district -v
the payload is the user profile (as I get with
https://apps.dhis2.org/demo/api/users/OYLGMiazHtW.json),
Hi Jose
This is partly due to our current implementation of PATCH, and partly due
to our somewhat strange User/UserCredentials model.
I will not be able to fix this right now, but will try and have a fix in
for our 2.19 release (together with proper PATCH support).
For now, you can still update
That means that it worked, as the password you have sent is in clear text.
It is just a warning, but if you see this, then try and login as the
user with the new password and it should be fine.
On Wed, Feb 11, 2015 at 3:57 PM, Jose Garcia Muñoz josem...@gmail.com wrote:
Thanks Lars,
now I
Thanks Lars,
now I am getting the following output in the tomcat log
* WARN 2015-02-11 15:53:49,477 Encoded password does not look like BCrypt
(BCry
ptPasswordEncoder.java [http-apr-8080-exec-10])
and the same error in the curl output...
On Wed, Feb 11, 2015 at 2:33 PM, Lars Helge Øverland
Hi again,
I tried in the Sierra Leone demo, with the following curl command:
curl.exe -X PATCH -d @c:\file.json -u admin:district
https://apps.dhis2.org/demo/api/users/OYLGMiazHtW/userCredentials; -H
Content-Type: application/json
with the following payload
{
userCredentials:
{password:
Hi Jose
I've been looking at this for a while now, and its not related to PATCH at
all, but there is something weird that is happening with userCredentials..
I will continue looking into it, and hopefully provide a fix today
--
Morten
On Thu, Feb 12, 2015 at 4:33 AM, Jose Garcia Muñoz
An example can be seen under user account invitations in web api docs:
https://www.dhis2.org/doc/snapshot/en/developer/html/ch01s27.html#d5e3604
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe
Thanks Lars, Morten,
Now the payload I am using is:
{
userCredentials:
{password: new_passwd,
id: AMuabF1Lrct,
name: user_name,
code: user_code,
created: 2014-11-27T18:24:05.888+, (Do I need this?)
lastUpdated: 2015-02-11T11:57:58.116+} (Do I need this?)
}
But still
sure,
curl.exe -X PATCH -d @c:\file.json -u myuser:mypasswd
http://localhost:8080/dhis/api/users/zNdlm77vil8/userCredentials;
On Wed, Feb 11, 2015 at 2:01 PM, Morten Olav Hansen morte...@gmail.com
wrote:
Can you give me the full cURL command you are using for this? including
headers etc
You need to include the content-type of what you are sending.
-H Content-Type: application/json
--
Morten
On Wed, Feb 11, 2015 at 8:08 PM, Jose Garcia Muñoz josem...@gmail.com
wrote:
sure,
curl.exe -X PATCH -d @c:\file.json -u myuser:mypasswd
Can you give me the full cURL command you are using for this? including
headers etc
--
Morten
On Wed, Feb 11, 2015 at 7:07 PM, Jose Garcia Muñoz josem...@gmail.com
wrote:
Thanks Lars, Morten,
Now the payload I am using is:
{
userCredentials:
{password: new_passwd,
id: AMuabF1Lrct,
ups... :) You are right, I completely forgot the Content-Type, sorry.
Almost there. The tomcat console gives me the following message:
* INFO 2015-02-11 14:23:26,119 'devapp' update org.hisp.dhis.user.User,
name: , uid: zNdlm77vil8 (AuditLogUtil.java [http-apr-8080-exec-9])
So everything
Hi Jose,
try specifying username instead of name property.
Lars
On Wed, Feb 11, 2015 at 2:32 PM, Jose Garcia Muñoz josem...@gmail.com
wrote:
ups... :) You are right, I completely forgot the Content-Type, sorry.
Almost there. The tomcat console gives me the following message:
* INFO
Thanks for the clarification.
Unfortunately it is still not working (likely because I am doing something
wrong). So the call to the API that I tried is:
api/users/zNdlm77vil8/userCredentials
and the payload:
{
password: the_new_passwd,
id: AMuabF1Lrct, (the id of the user credentials)
Hi
No, this will not work.. as listed in the docs you need to also use the
same property name in your JSON, so it should be:
{
userCredentials: { ... same as before }
}
--
Morten
On Wed, Feb 11, 2015 at 2:12 AM, Jose Garcia Muñoz josem...@gmail.com
wrote:
Thanks for the clarification.
Yes, sorry. You will need to patch the full userCredentials part of the
user (its at least a bit smaller than the whole user payload)
--
Morten
On Tue, Feb 10, 2015 at 1:54 AM, Lars Helge Øverland larshe...@gmail.com
wrote:
Hi, it should be on the userCredentials object.
On Mon, Feb 9, 2015
Hi, it should be on the userCredentials object.
On Mon, Feb 9, 2015 at 7:17 PM, Jose Garcia Muñoz josem...@gmail.com
wrote:
Thanks Jason, Morten,
Morten, I have tried with the 2.18. However, I am getting the following
answer Property password does not exist on org.hisp.dhis.user.User
On
Thanks Jason, Morten,
Morten, I have tried with the 2.18. However, I am getting the following
answer Property password does not exist on org.hisp.dhis.user.User
On Mon, Feb 9, 2015 at 12:58 PM, Jason Pickering
jason.p.picker...@gmail.com wrote:
Easiest was would be to GET the current payload
Thanks Jason,
sorry, and how should it work? I tried with the following call...
curl.exe -d @user.json http://localhost:8080/dhis/api/users/oEiOvqVp3A9;
-H Content-Type:application/json -u myuser:mypasswd -v
where the user.json file just contains
{
username: the_user_name,
password:
You need to send the full payload. Are you on 2.18? you could use PATCH for
this now.. something like
{
password: new-password
}
curl -X PATCH -d @password.json -u user:pass
http://localhost:8080/api/users/ID/password
(untested, but should work)
--
Morten
On Mon, Feb 9, 2015 at 6:43 PM,
Easiest was would be to GET the current payload of the user,modify the
password to what you want and the POST this payload back, if you are on
2.17.
Regards,
Jason
On Feb 9, 2015 12:56 PM, Jose Garcia Muñoz josem...@gmail.com wrote:
Thanks Jason,
nope, I am using the 2.17. But will migrate
Thanks Jason,
nope, I am using the 2.17. But will migrate to the 2.18 this afternoon.
Will test it and let you know.
So in the 2.17 I would need to introduce all the information of the user
again in the payload?
Thanks
Jose
On Mon, Feb 9, 2015 at 12:46 PM, Morten Olav Hansen morte...@gmail.com
Hi devs,
I didn't see anything in the documentation in that regard. I could only
find out the user replication as the only way to specify a user passwd
using the API. Am I correct?
Thanks
Jose
___
Mailing list: https://launchpad.net/~dhis2-devs
Post to
Hi Jose,
Yes, it is possible to send the plain-text password of a user to the
system using the API, which will then hash the password for you and
persist it in the database.
Best regards,
Jason
On Mon, Feb 9, 2015 at 1:04 AM, Jose Garcia Muñoz josem...@gmail.com wrote:
Hi devs,
I didn't
26 matches
Mail list logo
