Roles API
Ivan R. Judson
judson at mcs.anl.gov
Tue Aug 12 13:09:54 CDT 2003
Eric,
At first pass this looks like a good API. The only point that sprang to mind
immediately was finding someplace in the object hierarchy these can live
only once. The objects that need this immediately are:
VenueServer, and
Venue
But I can easily see shared apps, data, services, etc all wanting to use
these same API's.
Have you thought about how these will get introduced?
--Ivan
> -----Original Message-----
> From: owner-ag-dev at mcs.anl.gov
> [mailto:owner-ag-dev at mcs.anl.gov] On Behalf Of Eric Olson
> Sent: Tuesday, August 12, 2003 11:24 AM
> To: ag-dev at mcs.anl.gov
> Subject: Roles API
>
>
>
> Here is the current exposed Roles soap API for the Venue.
> They can easily be added, removed, or renamed at this time, so take a
> quick look if you have a minute. I beliebe you have to be an
> Administrator to access all of them except the last one.
>
> Venue.
> AddSubjectToRole(subject, role_string)
> RemoveSubjectFromRole(subject, role_string)
> SetSubjectsInRole(subject_list, role_string):
> AddRole(role_string)
> GetUsersInRole(role_string)
> (It seems both "Subject" and "User" are used, which is better?)
> GetRoleNames()
> returns list of strings
> GetAvailableGroupRoles()
> returns groups the venue knows about as list of strings.
> examples include All Users or Server Administrators
>
>
> Users also probably would like to know which roles they are in.
> -- specifically so the venueclient can know if the user is a venue
> administrator and if so, provide a button to administrate the venue.
> I'm proposing something like the following:
>
> DetermineRoles(subject="")
> returns a list of role names that the user is in.
> only authorized for this call if you are requesting your
> own roles or
> you are an administrator.
>
> Comments requested,
> Eric
>
More information about the ag-dev
mailing list