Mailing-List: contact users-help@archiva.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@archiva.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Problem with 1.1.1 - Login does not work
Date: Wed, 13 Aug 2008 10:51:10 +0200
Message-ID: <7CA45EC6F903DA4EB4ADB6D08D24B0F633D720B2@fnbfdtmx01.fnb.co.za>
In-Reply-To: <361C9980A68036489230480B6BF62CF501C7E9C6@falkxchg.falkland.de>
Thread-Topic: Problem with 1.1.1 - Login does not work
Thread-Index: Acj9HK1pYm/DNg78RCCp/vmEPdCxfQABGy8wAAAj8GA=
From: "Jeffery, Mark" <MJeffery@fnb.co.za>
To: <users@archiva.apache.org>

What database are you using ?

-----Original Message-----
From: von Janowsky, Simon [mailto:vonJanowsky@consist.de]=20
Sent: 13 August 2008 10:48
To: users@archiva.apache.org
Subject: AW: Problem with 1.1.1 - Login does not work


Just for clarification, I did not upgrade archiva, I set up a new instanc=
e.

Greetings,
Simon.=20


-----Urspr=FCngliche Nachricht-----
Von: Arnaud HERITIER [mailto:aheritier@gmail.com]=20
Gesendet: Mittwoch, 13. August 2008 10:08
An: users@archiva.apache.org
Betreff: Re: Problem with 1.1.1 - Login does not work

I had a similar weird behavior when upgrading yesterday I was able to log=
on with my accounts retreived from my old database but when I had a look =
at them they were several of them marked as locked It was also the case f=
or admin but it appeared only on the screen when we edit it (not in the l=
ist - perhaps because it is a permanent account).
When account were locked, I was able to logon but search and browse sent =
me an error because I didn't have required credentials...

I think this is a problem during the migration and this is a false lock.
I think we can reproduce it by created several accounts in an archiva 1.0=
.2 and trying to upgrade it in 1.1.

Arnaud


On Wed, Aug 13, 2008 at 9:56 AM, von Janowsky, Simon <vonJanowsky@consist=
.de
> wrote:

>  Hello,
> I could solve the problem by logging in as another administrator.
> Didn't know the password of admin2 last night....
> In the User Management section the first "admin" was locked then...
> I unlocked the admin, but when trying to log in again, he was locked=20
> again. After changing "admin"s password login worked fine.
>
> Now I am a little confused, is this a bug?
> The behaviuor is exact the same as MRM-728, since the login also=20
> failed silently.
>
> By the way, Archiva is really great :-)
>
> Greetings,
> Simon.
>
>
> Was this working for you in a previous version? Do you have anything=20
> in common/different to the MRM-728 report?
>
> Thanks,
> Brett
>
> 2008/8/13 von Janowsky, Simon <vonJanowsky@consist.de>:
> >  Hi all,
> > after setting up the new Archiva version 1.1.1, everything worked
> fine,
> > Repositories, Proxy connectory and users were created.
> > But now I am not able to login anymore, when I use the admin=20
> > account, the screen refreshes and only the "Find Part" in the left=20
> > menu appears. When loggin in as a registered user and Global Repo=20
> > manager the same happens, it is only possible to edit the account=20
> > details (what is not seen being admin). I found
> this
> > or a similar bug in the bugtracking system (issue MRM-728)....
> > Is this unresolved? How can I fix this? By the way I use Tomcat=20
> > 6.0.16 to deploy archiva.
> >
> > Help would really be appreciated.
> >
> > With kind regards,
> > Simon von Janowsky
> >
> >
> >
>
>


--
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com =
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................


To read FirstRand Bank's Disclaimer for this email click on the following=
=20address or copy into your Internet browser:=20
https://www.fnb.co.za/disclaimer.html=20

If you are unable to access the Disclaimer, send a blank e-mail to
firstrandbankdisclaimer@fnb.co.za and we will send you a copy of the Disc=
laimer.