https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/AAA-44 aaa <p>As explained in this wiki page:<br/> <a href="https://wiki.opendaylight.org/view/Connecting_to_IdmLight_with_psql" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.opendaylight.org/view/Connecting_to_IdmLight_with_psql</a></p> <p>Changing a user password is complex. This should presumably be an easier task as every user of OpenDaylight will want to do that immediately after installing it.</p> <p>Operating System: All<br/> Platform: All</p> AAA-44

Changing a user password requires external tools

Bug Resolved Cannot Reproduce Ryan Goulding Colin Dixon Tue, 30 Jun 2015 19:55:51 +0000 Thu, 21 Mar 2019 11:56:41 +0000 Mon, 26 Sep 2016 13:34:10 +0000 General 0 3 <p>Yesterday I verified that this works to update a user record:</p> <p>curl -X PUT -s -H "Content-type:application/json" --data-binary @user.json https//&lt;controller&gt;:8181/auth/v1/users/1</p> <p>Contents of user.json:<br/> {<br/> "name":"newadmin",<br/> "description":"newadmin test user",<br/> "enabled":"true",<br/> "email":"theoneandonlyadmin@gmail.com",<br/> "password":"foobar"<br/> }</p> <p>Improper behavior was exhibited due to <a href="https://jira.opendaylight.org/browse/OVSDB-143" title="Need to define OVSDB Clustering/Data Persistence Behavior" class="issue-link" data-issue-key="OVSDB-143"><del>OVSDB-143</del></a> which has since been resolved in stable/lithium and master. I am closing this out now as "Works for me".</p> <p>Created this page to document this better:<br/> <a href="https://wiki.opendaylight.org/view/AAA:Changing_Account_Passwords" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.opendaylight.org/view/AAA:Changing_Account_Passwords</a></p> <p>I have an off-topic question.</p> <p>&gt; <a href="https://wiki.opendaylight.org/view/AAA:Changing_Account_Passwords" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.opendaylight.org/view/AAA:Changing_Account_Passwords</a></p> <p>Both methods require ODL to be started at least once with admin:admin default credentials, which is not secure.</p> <p>Is there an Improvement item somewhere, which asks for idmlight.db.mv.db to be created already during </p> {project} <p><del>distribution</del></p> {stream} <p> job run, so that the file is already present in released tar.gz file (thus available forthe second method)?</p> <p>The easiest way would be for AAA project to create and upload the file to Nexus, and integration/distribution would copy it in.</p> <p>This is a good idea. I will create a trello card to address this.</p> <p>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.</p> <p>Added here:<br/> <a href="https://trello.com/b/kkUQaCv6/aaa-berylium" class="external-link" target="_blank" rel="nofollow noopener">https://trello.com/b/kkUQaCv6/aaa-berylium</a></p> <p>I will work with the team to get these issues addressed. If you are interested in helping with implementation, please let me know!</p> <p>&gt; If you are interested in helping with implementation, please let me know!</p> <p>I do not really have time to write code, but I can perhaps comment and review.<br/> My trello user is <a href="https://trello.com/vratkopolak" class="external-link" target="_blank" rel="nofollow noopener">https://trello.com/vratkopolak</a> in case you want me to have write access to cards on your board.</p> <p>Now I think it is better for the packaged file to have a different name, for example "example.idmlight.db.mv.db".<br/> The point is to be more resilient against accidental "tar xf" destroying configured credentials without anyone noticing.</p> <p>Hi</p> <p>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.</p> <p>Step 1: curl -u admin:admin <a href="http://localhost:8181/auth/v1/users" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8181/auth/v1/users</a></p> <p>Step 2: cat user.json <br/> {<br/> "name":"admin",<br/> "description":"admin account",<br/> "enabled":"true",<br/> "email":"",<br/> "password":"newadminpassword"<br/> }</p> <p>Step 3: curl -u admin:admin -X PUT -H "Content-Type: application/json" --data-binary @./user.json <a href="http://localhost:8181/auth/v1/users/1" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8181/auth/v1/users/1</a></p> <p>Please suggest.</p> <p>The id is wrong in your URL:</p> <p><a href="http://localhost:8181/auth/v1/users/1" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8181/auth/v1/users/1</a></p> <p>should be:</p> <p><a href="http://localhost:8181/auth/v1/users/admin@sdn" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8181/auth/v1/users/admin@sdn</a></p> <p>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:</p> <p>python etc/idmtool -h</p> <p>&gt; there is a script that does this now located in the etc folder</p> <p>Why "etc"? I believe "bin" is much better folder for executable scripts.</p> Development External issue ID 3911 External issue URL Rank 0|i023r3: