Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] Similar to: Changing a userName(subjectId) -

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] Similar to: Changing a userName(subjectId) -

Chronological Thread 
  • From: "Hyzer, Chris" <>
  • To: Jeffrey Crawford <>
  • Cc: "" <>
  • Subject: RE: [grouper-users] Similar to: Changing a userName(subjectId) -
  • Date: Wed, 8 Jun 2016 15:21:41 +0000
  • Accept-language: en-US
  • Authentication-results: spf=none (sender IP is ) ;
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

Bert, can you please reply to this one?





From: Jeffrey Crawford [mailto:]
Sent: Wednesday, June 08, 2016 11:12 AM
To: Hyzer, Chris <>
Subject: Re: [grouper-users] Similar to: Changing a userName(subjectId) -


Actually, we've been having some trouble with renames. We don't use the user id for our Grouper implementation, we use our IdM identifier which doesn't change on renames. However this causes problems when a user id is renamed but not our IdM identifier. Grouper sees the changes of course since it looks up people via the identifier. However the provisioner doesn't know the name changed so it has no way to change our LDAP group with the new name. (Although this may be achievable with the data integrity plugin, it doesn't help our POSIX groups).

is there a way to have memberChangeSubject simply recalculate a an existing ID that doesn't change for the provisioned groups?


Both pilots and IT professionals require training and currency before charging into clouds!



On Wed, Jun 8, 2016 at 7:29 AM, Hyzer, Chris <> wrote:

Hmmm, if you don't change the subjectIds or identifiers or the source name, then nothing should change in the table...  if you need to change the subjectId used, you can do something like this :)


-----Original Message-----
From: Jeff McCullough [mailto:]
Sent: Tuesday, June 07, 2016 5:01 PM
To: Hyzer, Chris <>
Subject: Re: [grouper-users] Similar to: Changing a userName(subjectId) -

To piggy back on this, is something akin to this the recommended way to change a subject source? We have been using LDAP as our subject source, and may change this to a DB view.


> On Oct 28, 2015, at 4:55 AM, Chris Hyzer <> wrote:
> I think you can just change the subject_id field in the database table grouper_members for that record.  The reason for memberChangeSubject is there will be a foreign key problem if the new subject exists.  Shilen, let me know if you disagree here.  Kumi, if this is what you want to do, you can do that directly in the DB or I can give you GSH to do this...  note, if the old subject is still being resolved and used after you make the change, it will create a new grouper_members record for the old subject again.
> Thanks,
> Chris
> -----Original Message-----
> From: [mailto:] On Behalf Of
> Sent: Tuesday, October 27, 2015 7:43 PM
> To:
> Subject: [grouper-users] Changing a userName(subjectId)
> Hello,
> I'm hoping that someone can point me in the right direction.  I'd like to be
> able to update a username (subjectId) when user's name is updated in the data
> source.
> At first this MemberChangeSubject seemed like the solution,
> but it looks like the new and old subject must already exist and it updates
> the membership details, not the subject details.  In my case, the new subject
> doesn't exist.  Is there a way to update the subjectId of the old/existing
> subject?
> Thanks,
> Kumi


Archive powered by MHonArc 2.6.16.

Top of Page