Operating System: All
Platform: All

Yesterday I verified that this works to update a user record:

curl -X PUT -s -H "Content-type:application/json" --data-binary @user.json https//<controller>:8181/auth/v1/users/1

Contents of user.json:
{
"name":"newadmin",
"description":"newadmin test user",
"enabled":"true",
"email":"theoneandonlyadmin@gmail.com",
"password":"foobar"
}

Improper behavior was exhibited due to OVSDB-143 which has since been resolved in stable/lithium and master. I am closing this out now as "Works for me".

Created this page to document this better:
https://wiki.opendaylight.org/view/AAA:Changing_Account_Passwords

I have an off-topic question.

> https://wiki.opendaylight.org/view/AAA:Changing_Account_Passwords

Both methods require ODL to be started at least once with admin:admin default credentials, which is not secure.

Is there an Improvement item somewhere, which asks for idmlight.db.mv.db to be created already during

distribution

job run, so that the file is already present in released tar.gz file (thus available forthe second method)?

The easiest way would be for AAA project to create and upload the file to Nexus, and integration/distribution would copy it in.

This is a good idea. I will create a trello card to address this.

We will also need to add a script to do the "second method" which has changed just the other day since passwords are now salted and encrypted using MD5. I will also add a card for this.

Added here:
https://trello.com/b/kkUQaCv6/aaa-berylium

I will work with the team to get these issues addressed. If you are interested in helping with implementation, please let me know!

> If you are interested in helping with implementation, please let me know!

I do not really have time to write code, but I can perhaps comment and review.
My trello user is https://trello.com/vratkopolak in case you want me to have write access to cards on your board.

Now I think it is better for the packaged file to have a different name, for example "example.idmlight.db.mv.db".
The point is to be more resilient against accidental "tar xf" destroying configured credentials without anyone noticing.

Hi

I am trying to modify the password by performing the steps mentioned above but still when I am trying to log in ODL, I am unable to do so with the new password.

Step 1: curl -u admin:admin http://localhost:8181/auth/v1/users

Step 2: cat user.json
{
"name":"admin",
"description":"admin account",
"enabled":"true",
"email":"",
"password":"newadminpassword"
}

Step 3: curl -u admin:admin -X PUT -H "Content-Type: application/json" --data-binary @./user.json http://localhost:8181/auth/v1/users/1

Please suggest.

The id is wrong in your URL:

http://localhost:8181/auth/v1/users/1

should be:

http://localhost:8181/auth/v1/users/admin@sdn

Also, there is a script that does this now located in the etc folder upon feature installation. You can invoke the help function by this:

python etc/idmtool -h

> there is a script that does this now located in the etc folder

Why "etc"? I believe "bin" is much better folder for executable scripts.