IMHO, it is by design. The org admin should assign manually before the normal user can manage their servers by spacewalk.
On 10/25/2014 05:12 AM, Avi Miller wrote: > Hey guys, > > I'm not sure if I'm doing something wrong, or if this is actually an > issue/oversight: I've setup a central Spacewalk instance and split it into > multiple organisations (so that each org can manage itself). However, when an > Org Admin creates a new activation key, the "normal" users, i.e. user > accounts without any roles selected, can't see the activation keys that are > available. > > Is this by design? I want individual users to be able to register and manage > their own servers, but not see/manage anyone else's servers. If they can't > see the available activation keys though, I'm not sure how they're suppose to > know how to register a server. :) > > Or, is the idea to make each user an Activation Key Administrator? If so, > that means an organisation could land up with multiple, almost-duplicate keys. > > Happy for any insight on this. > > Thanks, > Avi > > -- > Oracle <http://www.oracle.com> > Avi Miller | Product Management Director | +61 (3) 8616 3496 > Oracle Linux and Virtualization > 417 St Kilda Road, Melbourne, Victoria 3004 Australia > > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list > _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
