[Building Sakai] SAK-17260

[Maurer, Christopher Wayne]

Zhen,
What you just described is not what I'm experiencing.  My user always comes through as provided (with the provided role) and I have no option to remove the user.

Chris

From: Zhen Qian <zqian at umich.edu<mailto:zqian at umich.edu>>
Date: Wed, 27 Apr 2011 10:39:39 -0400
To: Chris Maurer <chmaurer at iupui.edu<mailto:chmaurer at iupui.edu>>
Cc: <sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>>
Subject: Re: [Building Sakai] SAK-17260


Chris:

It is a general problem and not specific to one AuthzGroup provider implementation.

I think it is open to discussion whether the overridden role should be reserved or not if it is different from that in provider definition.

SAK-17260 will reserve the current role, but show all the provider information about the user. The "Remove" column is still enabled for the user. After removal, the user is still shown with role reverted back to the provided role.

KNL-403 removes local role definition for provided user ONLY IF the local role == provided role. In order words, it won't do anything if user is first added as roleA and later provided with roleB.

Based on the description of SAK-17260, I don't think it conflicts with KNL-403...

Thanks,

- Zhen







On Wed, 27 Apr 2011 13:57:57 +0000, "Maurer, Christopher Wayne" <chmaurer at iupui.edu<mailto:chmaurer at iupui.edu>> wrote:

https://jira.sakaiproject.org/browse/SAK-17260
This issue was fixed over a year ago, so perhaps no one really remembers, but I had some concerns as I see how things are working on our local 2.7 version.
I'm not sure if it's just due to the special provider that we're using here, but the behavior that I now see is that a user that is an actual member of a site will have their role overridden by the role coming from the provider.  Is that really what is intended?  If so, maybe we should adopt a solution similar to how the provided role is determined (by an ordered list – siteRoleResolutionOrder – so that the provided role would be chosen only if it were higher in the list then the native site role.
Am I way out there with this requirement?  Maybe this isn't an issue with the standard group providers and is only an issue with the custom one we wrote!
Chris


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20110427/74b5d5a4/attachment.html