AzMan scope level application groups seem to be broken
- From: "Jim Pierson" <jpierson@xxxxxxxxxxxxxxxxxxx>
- Date: Sun, 20 May 2007 10:33:57 -0400
I've not been able to find anything on this, so it's time to ask for help.
I have an AzMan store in an ADAM instance using ADAM principals. There is
one application defined
and a multitude of scopes. ApplicationGroups are defined at all three
levels (store, app & scope).
If I assign an ADAM principal as a member of either a store or app level
group and include that group
in a role assignment, all is well. GetAssignedScopesPages, GetRoles and
AccessCheck return exactly
what they should.
However, if I assign a principal to an application group at the scope level
and use that group in a role
assignment, I get absolutely nothing back on calls to the above methods.
It's as if the ClientContext
interface is completely ignoring ApplicationGroups at the scope level.
At first I said no big deal, I'll just put all my app groups at the app
level but now it's becoming a
problem with administration. Each scope is a department and without scope
level app groups,
delegating administration to department heads is going to be problematic at
best.
Any help would be appreciated.
.
- Prev by Date: X.509 Certificate based authentication
- Next by Date: Re: prevent duplicate logins
- Previous by thread: X.509 Certificate based authentication
- Next by thread: Re: prevent duplicate logins
- Index(es):
Relevant Pages
|
