Hi, The most important is to know if you pass in resetPassword method when you use it. That's located in class DefaultUserService method resetPassword (that's part of redback sources: https://svn.apache.org/repos/asf/archiva/redback/redback-core/). Do you receive any emails when asking for a "password reset" ? Do you any javascript errors in your browser console ?
Thanks! 2012/10/9 Jeff <[email protected]>: > I pulled the source and have enabled remote debugging on the server. I'll > try to drill into it. If you can point me to the file/module I should > focus on, it would help. :) You need to have a look a > > On Tue, Oct 9, 2012 at 1:06 AM, Olivier Lamy <[email protected]> wrote: > >> 2012/10/9 Brett Porter <[email protected]>: >> > >> > On 09/10/2012, at 4:04 PM, Jeff <[email protected]> wrote: >> > >> >> Okay, I copied the database to my system (host is headless Linux), >> >> installed latest SquirrelSQL client copied the password field from >> another >> >> user that I remembered and was able to log in. >> >> >> >> THANK YOU! >> >> >> >> However, when I attempt to change the password, it tells me: >> >> >> >> Password provided does not match existing. >> >> >> >> I can log out and log in still using the password I copied but all >> attempts >> >> to change it result in this error...unless I pick a password I've used >> >> previously. >> >> >> >> Also, I don't want service accounts (users) that are used specifically >> for >> >> our deployment scripts to have to change the password. >> >> >> >> My archiva installation/configuration is at /archiva/conf. I created a >> >> security.properties file there and have the following settings but it >> still >> >> says the user requires a password change if I attempt to log in or if I >> >> "Manage" the users, the 3 service account users show that the "Force >> >> password change" is enabled but the setting won't stick if I change it. >> > >> > I wonder if these could be bugs in the new UI? Obviously some >> significant changes there and something might have crept through. You could >> always point 1.4-M2 or earlier at the users database and see if it acts as >> expected... or file a bug regardless. >> > >> could be a bug in the new ui :-). >> @Jeff what are the steps to reproduce that ? >> Normally using reset link must send an email to you. >> Can you create a jira with all the steps ? >> > I'd add the deployment user to the unlockable accounts, which will avoid >> the issue of password change over time (but not help with the forced >> password change). >> > >> > - Brett >> > >> > -- >> > Brett Porter >> > [email protected] >> > http://brettporter.wordpress.com/ >> > http://au.linkedin.com/in/brettporter >> > http://twitter.com/brettporter >> > >> > >> > >> > >> > >> >> >> >> -- >> Olivier Lamy >> Talend: http://coders.talend.com >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> > > > > -- > Jeff Vincent > [email protected] > See my LinkedIn profile at: > http://www.linkedin.com/in/rjeffreyvincent > I ♥ DropBox <http://db.tt/9O6LfBX> !! -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy
