>
> Additionally there is the fact that admins are inherently lazy.
> I'd rather hack away for 3 days on something until it works as
> expected/can be automated/integrated than do it manually.
Ouch! I hope there are no hard working admins subscribed here, there might
be a rebellion.
Is Wendy's s
- "Wendy Smoak" wrote:
> 2011/1/20 Igor Galić :
> >> > So you would grant repository 'observer' or 'manager' roles to
> each
> >> > person in Archiva as needed.
> >
> > Which sounds like a big pain for an admin );
>
> If you have lots of users, I agree it's going to be a pain to edit
> each
2011/1/20 Igor Galić :
>> > So you would grant repository 'observer' or 'manager' roles to each
>> > person in Archiva as needed.
>
> Which sounds like a big pain for an admin );
If you have lots of users, I agree it's going to be a pain to edit
each one to grant them the correct roles.
In Contin
Really? I would like to understand. I can see this for Continuum if you're
managing roles on a per project basis, but for Archiva? Ultimately, unless
you're loading an ldap group that grants many resources to someone (maybe
not a great idea for other management reasons) you should be talking about
- "Brent Atkinson" wrote:
> Wendy beat me to it.
>
> I believe she is correct. You can configure anonymous read-only by
> granting
> Global Repo Observer to your configured guest account, but selective
> roles
> and privileges are not automatically granted based on ldap groups at
> the
> mo
