According to the wiki page at
https://fedorahosted.org/cobbler/wiki/AuthorizationWithOwnership ,
anyone who is in users.conf can create new cobbler objects. I've had
opposite luck in my 1.6.6 production installation.
I'm working with a testuser listed in [testgroup] in users.conf. The
user can create profiles only when moved to [admin]. Same problem
through the web interface or the XMLRPC API. Here's my cobblerd.log
output:
2010-03-05 14:57:37,603 - api - login attempt; user(testuser)2010-03-05
14:57:37,603 - api - authenticate; ['testuser', True]
2010-03-05 14:57:37,604 - api - login succeeded; user(testuser)
2010-03-05 14:57:47,263 - api - new_repo; user(testuser)2010-03-05
14:57:47,263 - api - calling authorize for resource ['new_repo', None,
None]; user(testuser)
2010-03-05 14:57:47,264 - api - authorization result: True; user(?)
2010-03-05 14:58:06,184 - api - calling authorize for resource
['modify_repo', <cobbler.item_repo.Repo instance at 0x1d35758>,
'name';
user(testuser)r):56,692 - api - get_profiles; user(?)
2010-03-05 14:58:06,184 - api - Exception occured:
cobbler.cexceptions.CX2010-03-05 14:58:06,184 - api - Exception value:
'user does not have access to resource: modify_repo'
2010-03-05 14:58:06,185 - api - Exception Info:
File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 1567,
in _dispatch
return method_handle(*params) File
"/usr/lib/python2.4/site-packages/cobbler/remote.py", line 1409, in
modify_repo
self.check_access(token, "modify_repo", obj, attribute)
File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 1013,
in check_access rc = self.__authorize(token,resource,arg1,arg2)
File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 1044,
in __authorize raise CX(_("user does not have access to resource:
%s") % resource)
Any ideas?
-CG