[
http://jira.codehaus.org/browse/MRM-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121521
]
Brett Porter commented on MRM-668:
----------------------------------
I understand the thought behind the fix, and think it's a good enough
workaround.
But I also worry it's just masking something else longer term - as your earlier
question indicated: "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?" :)
Maybe one of the Redback guys could answer that? It really seems like it should
only be set once.
> 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
> Assignee: Maria Odea Ching
> Priority: Blocker
> Fix For: 1.0.1
>
>
--
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
