[
http://jira.codehaus.org/browse/MRM-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109809
]
Wendy Smoak commented on MRM-539:
---------------------------------
>From MRM-398, Brett's comment:
I would suggest the best way to do this is to allow assignment of roles as a
step in repository creation rather than introducing a new flag that is tied to
a role.
> Make security level of repository more obvious on admin/repositories screen.
> ----------------------------------------------------------------------------
>
> Key: MRM-539
> URL: http://jira.codehaus.org/browse/MRM-539
> Project: Archiva
> Issue Type: Improvement
> Components: Users/Security
> Affects Versions: 1.0-beta-2
> Reporter: Joakim Erdfelt
> Priority: Minor
>
> Make the repositories screen show the security level of the repository.
> Make the repository configuration process simplify the role assignments.
> Pre-configure the default-archiva.xml repositories for public, read-only
> security level.
> Technical Details:
> 1) Add a field ManagedRepositoryConfiguration.security (with possible value:
> public-read-only, public-read-write, access-controlled)
> 2) Configure the default-archiva.xml with that field set true.
> 3) Configure the UI for repositories to show/set/change that value.
> 4) Integrate the guest user role assignments to that field.
--
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
