You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Stephen Coy (JIRA)" <ji...@codehaus.org> on 2008/12/09 23:54:19 UTC

[jira] Commented: (MRM-728) After successful admin login archiva reacts as if user is guest

    [ http://jira.codehaus.org/browse/MRM-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157499#action_157499 ] 

Stephen Coy commented on MRM-728:
---------------------------------

I've observed this problem in both Continuum 1.2.2 and Archiva 1.1.2. 

I tracked it down to the clock on the VM instance running them being wrong by several hours. This causes the applications to send cookies which expire as soon as the browser receives them.




> After successful admin login archiva reacts as if user is guest
> ---------------------------------------------------------------
>
>                 Key: MRM-728
>                 URL: http://jira.codehaus.org/browse/MRM-728
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: linux
>            Reporter: Robin Roos
>            Priority: Critical
>             Fix For: 1.x
>
>         Attachments: advancedprivacysettings.jpg, archiva.log, archiva.log.debug.signon.txt
>
>
> I ran Archiva on my windows box and, after configuring the admin user, I was able to login.  The header of the web page identified me as Administrator (admin) and I could see all the expected functions on the left hand frame.  So far so good.
> I had Archiva installed on a linux box and started.  I surfed to the box from Windows and configured the admin user.  But when I logged in as admin I got a page with only Search/FindArtifact/Browse functions.  The header page reads "Login - Register".  It is as if I am not logged in and am seeing the guest functions.  Note that if I log in with a deliberately incorrect password then I get an error message as expected.  But logging in with the right credentials appears to fail silently.
> As a result I cannot deploy any artifacts into Archiva, I cannot roll out the maven/subversion/archiva based edition of our in-house project, and I fear my time is limited!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira