Mailing-List: contact users-help@archiva.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@archiva.apache.org
To: users@archiva.apache.org
From: =?UTF-8?B?SsO2cmc=?= Schaible <joerg.schaible@gmx.de>
Subject: Re: Archiva 2.2.x, resetting password
Date: Wed, 17 Aug 2016 00:32:05 +0200
Lines: 37
Message-ID: <np0495$tad$1@blaine.gmane.org>
References: <CA+bF-zxzogLncuPfs124GFuz2+HjuT7=1XqnvLCyngsU8B7ouw@mail.gmail.com>
Reply-To: joerg.schaible@gmx.de
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8Bit
User-Agent: KNode/4.14.10
archived-at: Tue, 16 Aug 2016 22:32:18 -0000

Hi Thad,

Thad Humphries wrote:

> Despite earlier efforts to get Archiva to stop requiring password reset,
> it's done it again. Now neither user nor admin can get in and the "Reset
> Password" button seems to do nothing.
> 
> How can I clear the old passwords and reset the admin and users? Or (as
> done at least once before) must I blow it all away an reinstall?
> 
> Can't this "feature" be disable? There is *at most* only two of using
> this.

I had also a very annoying fight with this and I am only one. I found 
finally a location to turn the expiration off (at least I hope so):

================ %< ===============
$ sudo cat /var/lib/archiva/security.properties
security.policy.password.previous.count=0
security.policy.password.expiration.enabled=false
================ %< ===============

However, I was in the same situation as you and I finally created a new DB 
for the Archiva users, configured Archiva to use that one instead and let it 
recreate an admin and guest user (note, you have to turn off password 
expiration before). Then I exported the two JDOUSER* tables, dropped 
anything in these tables of the original DB and imported the data. After 
that I configured Archiva to use the original User DB again. Now I could 
login as admin again and was able to recreated my user.

Note: Always shut down Tomcat before you change something in the DB.

Hope this works for you also.

Cheers,
Jörg