[
http://jira.codehaus.org/browse/MRM-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121492
]
Maria Odea Ching commented on MRM-668:
--------------------------------------
Looks like it was from my fix in MRM-628, which caused this problem. I changed
the key to be looked up to get the security session in ArchivaXworkUser from
SecuritySystemConstants.SECURITY_SESSION_KEY to SecuritySession.ROLE (because
the security session's key is set to this). Both are the same security sessions
but set with different keys in the session map. Does anybody know when the
security session is set with SecuritySystemConstants.SECURITY_SESSION_KEY as
the key and when it is set with SecuritySession.ROLE as the key?
To handle this, I will put a check to lookup the security session from the
session map using both keys as shown below. This is in ArchivaXworkUser btw..
private SecuritySession getSecuritySession()
{
SecuritySession securitySession = (SecuritySession)
getContextSession().get( SecuritySession.ROLE );
if( securitySession == null )
{
securitySession = (SecuritySession) getContextSession().get(
SecuritySystemConstants.SECURITY_SESSION_KEY );
}
return securitySession;
}
Please advice if there might be anything that will be affected by this.. Thanks
> Repo browse and search isn't working in trunk and in archiva 1.0.1 release
> candidate
> ------------------------------------------------------------------------------------
>
> Key: MRM-668
> URL: http://jira.codehaus.org/browse/MRM-668
> Project: Archiva
> Issue Type: Bug
> Components: browser
> Affects Versions: 1.0.1
> Reporter: Maria Odea Ching
> Priority: Blocker
>
--
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
