Grouper Users - Open Discussion List

["Hyzer, Chris" <>]

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 :) 

Thanks
Chris

-----Original Message-----
From: Jeff McCullough 
[mailto:]
 
Sent: Tuesday, June 07, 2016 5:01 PM
To: Hyzer, Chris 
<>
Cc: 

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. 

Jeff
 
> 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, 
> https://spaces.internet2.edu/display/Grouper/Member+change+subject
> 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