Grouper Users - Open Discussion List

[David Langenberg <>]

--
David Langenberg
Identity & Access Management
The University of Chicago




On Apr 8, 2013, at 11:54 AM, Scott Koranda 
<>
 wrote:

> Hi,
> 
> On Mon, Apr 8, 2013 at 12:41 PM, David Langenberg 
> <>
>  wrote:
>> Hey Scott,
>> 
>> Would you query grouper_members table and see if the subject is in there?
> 
> Yes, it's in there:
> 
> mysql> select subject_id from grouper_members where subject_id like
> '%569df627%'\G
> *************************** 1. row ***************************
> subject_id: 569df627-ba3e-4cd4-b9bc-de1ba177ebe5
> 1 row in set (0.02 sec)
> 
> Should I be able to "reach" this using the usdu utility?

If you made it totally unresolvable, I believe so.  However, first I'd 
suggest trying to change the subject to use the correct id via 
memberChangeSubject

https://spaces.internet2.edu/display/Grouper/GrouperShell+%28gsh%29#GrouperShell%28gsh%29-Memberchangesubject

Deleting the memberships for that subject would also help.

Dave



> 
> Thanks,
> 
> Scott
> 
> 
>> 
>> Dave
>> 
>> --
>> David Langenberg
>> Identity & Access Management
>> The University of Chicago
>> 
>> 
>> 
>> 
>> On Apr 7, 2013, at 9:42 PM, Scott Koranda 
>> <>
>>  wrote:
>> 
>>> Hello,
>>> 
>>> I am using Grouper 2.1.3.
>>> 
>>> I have the PSP configured to provision stems, groups, and
>>> members to LDAP in the way that I need. Everything appears to be
>>> working and I see the results I expect when I run a bulk sync.
>>> 
>>> To be sure, however, I looked in the grouper_error.log file
>>> for any problems and I found these ERRORs:
>>> 
>>> 2013-04-08 03:16:53,401: [main] ERROR Psp.execute(1015) -  - Psp 'psp' - 
>>> Calc 
>>> CalcResponse[id=569df627-ba3e-4cd4-b9bc-de1ba177ebe5,status=failure,error=noSuchIdentifier,errorMessages={Unable
>>>  to calculate provisioned object.},requestID=2013/04/08-03:16:53.358]
>>> 2013-04-08 03:16:53,401: [main] ERROR Psp.execute(1017) -  - Psp 'psp' - 
>>> Calc XML:
>>> <psp:calcResponse xmlns:psp='http://grouper.internet2.edu/psp' 
>>> status='failure' requestID='2013/04/08-03:16:53.358' 
>>> error='noSuchIdentifier'>
>>> <errorMessage>Unable to calculate provisioned object.</errorMessage>
>>> <psp:id ID='569df627-ba3e-4cd4-b9bc-de1ba177ebe5'/>
>>> </psp:calcResponse>
>>> 
>>> 2013-04-08 03:16:53,401: [main] ERROR Psp.execute(1175) -  - Psp 'psp' - 
>>> Diff 
>>> DiffResponse[id=569df627-ba3e-4cd4-b9bc-de1ba177ebe5,status=failure,error=noSuchIdentifier,errorMessages={Unable
>>>  to calculate provisioned object.},requestID=2013/04/08-03:16:53.357]
>>> 2013-04-08 03:16:53,402: [main] ERROR Psp.execute(1177) -  - Psp 'psp' - 
>>> Diff XML:
>>> <psp:diffResponse xmlns:psp='http://grouper.internet2.edu/psp' 
>>> status='failure' requestID='2013/04/08-03:16:53.357' 
>>> error='noSuchIdentifier'>
>>> <errorMessage>Unable to calculate provisioned object.</errorMessage>
>>> <psp:id ID='569df627-ba3e-4cd4-b9bc-de1ba177ebe5'/>
>>> </psp:diffResponse>
>>> 
>>> 2013-04-08 03:16:53,402: [main] ERROR Psp.execute(1440) -  - Psp 'psp' - 
>>> Sync 
>>> SyncResponse[id=569df627-ba3e-4cd4-b9bc-de1ba177ebe5,status=failure,error=noSuchIdentifier,errorMessages={Unable
>>>  to calculate provisioned object.},requestID=2013/04/08-03:16:53.357]
>>> 2013-04-08 03:16:53,402: [main] ERROR Psp.execute(1442) -  - Psp 'psp' - 
>>> Sync SPML:
>>> <psp:syncResponse xmlns:psp='http://grouper.internet2.edu/psp' 
>>> status='failure' requestID='2013/04/08-03:16:53.357' 
>>> error='noSuchIdentifier'>
>>> <errorMessage>Unable to calculate provisioned object.</errorMessage>
>>> <psp:id ID='569df627-ba3e-4cd4-b9bc-de1ba177ebe5'/>
>>> </psp:syncResponse>
>>> 
>>> The same ERRORs happen each time I run a bulk sync, regardless
>>> of whether or not I have made any state changes.
>>> 
>>> Note that
>>> 
>>> 569df627-ba3e-4cd4-b9bc-de1ba177ebe5
>>> 
>>> is not a Grouper uuid. It is the rdn for one of my sources:
>>> 
>>> swampUuid=569df627-ba3e-4cd4-b9bc-de1ba177ebe5,ou=people,o=SWAMP,dc=cosalab,dc=org
>>> 
>>> Earlier in this deployment I did temporarily use 'swampUuid'
>>> as the Grouper ID attribute and I probably did add this user
>>> to a group using that ID.
>>> 
>>> Later, however, I switched to using another attribute (uid) as
>>> the Grouper ID.
>>> 
>>> So I thought perhaps the errors were due to a unresolvable
>>> subject. But the usdu utility does not return any unresolable
>>> subjects:
>>> 
>>> # sudo -u tomcat ./bin/gsh.sh -usdu -all
>>> Using GROUPER_HOME: /opt/grouper/grouper.api-2.1.3
>>> Using GROUPER_CONF: /opt/grouper/grouper.api-2.1.3/conf
>>> Using JAVA: java
>>> using MEMORY: 64m-750m
>>> Grouper starting up: version: 2.1.3, build date: 2013/03/11 02:24:03, 
>>> env: SWAMP
>>> grouper.properties read from: 
>>> /opt/grouper/grouper.api-2.1.3/conf/grouper.properties
>>> Grouper current directory is: /opt/grouper/grouper.api-2.1.3
>>> log4j.properties read from: 
>>> /opt/grouper/grouper.api-2.1.3/conf/log4j.properties
>>> Grouper logs are not using log4j: class 
>>> org.apache.commons.logging.impl.SLF4JLocationAwareLog
>>> grouper.hibernate.properties: 
>>> /opt/grouper/grouper.api-2.1.3/conf/grouper.hibernate.properties
>>> grouper.hibernate.properties: 
>>> grouper@jdbc:mysql://localhost:3306/grouper
>>> sources.xml read from: /opt/grouper/grouper.api-2.1.3/conf/sources.xml
>>> sources.xml groupersource id: g:gsa
>>> sources.xml groupersource id: grouperEntities
>>> sources.xml ldap source id:   SWAMP: ldap.properties
>>> #
>>> 
>>> Any ideas on what is causing the ERRORs in the
>>> grouper_error.log file?
>>> 
>>> Thanks,
>>> 
>>> Scott K
>>