[
http://jira.codehaus.org/browse/MRM-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joakim Erdfelt closed MRM-398.
------------------------------
Resolution: Fixed
Fixed in archiva/trunk revision
Newly created repositories are setup to be automatically assigned to the guest
user in read-only mode.
There are no provisions in redback to assign roles on first startup only.
Using redback ALONE to automatically assign the read-only role to the shipped
repositories is not possible.
Closing issue.
We can't hard-code the repository ids either, as corporate installations of
archiva will often pre-configure their archiva.xml before starting the first
time.
Created a new jira MRM-539 for alternative approach that was poo-poo'd in an
earlier comment by brett in this jira.
> configure guest access by default for pre-configured repositories
> -----------------------------------------------------------------
>
> Key: MRM-398
> URL: http://jira.codehaus.org/browse/MRM-398
> Project: Archiva
> Issue Type: Bug
> Components: Users/Security
> Affects Versions: 1.0-alpha-1
> Reporter: Brett Porter
> Assignee: Joakim Erdfelt
> Fix For: 1.0-beta-3
>
>
> I think it makes sense for repositories to be readable by guests by default
> for a good OOTB experience.
--
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
