Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] Deleting an orphaned subjectID

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] Deleting an orphaned subjectID

Chronological Thread 
  • From: Julio Polo <>
  • To: Chris Hyzer <>
  • Cc: "" <>
  • Subject: Re: [grouper-users] Deleting an orphaned subjectID
  • Date: Tue, 4 Aug 2015 11:26:09 -1000

I was mistaken in my assumption that it would not delete the member.  It appears the deletion takes place, despite the errors:

'WsDeleteMemberResult' => [
 { 'wsSubject' => { 'id' => '80345215' },
 'resultMetadata' => { 'success' => 'T', 'resultMessage' => 'Subject: WsSubjectLookup[ member=\'80345215\'/\'person\'/\'UH test LDAP\',
  cause=edu.internet2.middleware.subject.SubjectNotFoundException: subject not found: 80345215,
  subjectId=80345215] had problems: SUBJECT_NOT_FOUND',
  'resultCode' => 'SUCCESS' } } ]

I also just noticed the member change subject API call, which might be applicable to the situation I'm trying to address.



Julio Polo
Enterprise Middleware, Identity and Access Management
Information Technology Services
University of Hawaii

On Tue, Aug 4, 2015 at 3:07 AM, Chris Hyzer <> wrote:

Can you pass the subject sourceId and subjectId (not identifier) and then will it work?





From: [mailto:] On Behalf Of Julio Polo
Sent: Monday, August 03, 2015 5:34 PM
Subject: [grouper-users] Deleting an orphaned subjectID


We use LDAP as our subject source. When the subjectID is deleted from LDAP (after resolving duplicate identities for a person, we sometimes keep a different subjectID), this causes a subject-not-found error when we attempt to delete the deprecated subjectID from its groups.

Is there an option I can pass to the delete-member web service call to make it ignore the orphaned subjectID and to go ahed and remove the membership?


Archive powered by MHonArc 2.6.16.

Top of Page