...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<psp:calcRequest returnData='identifier'>
<psp:id ID='test.subject.1'/>
<psp:schemaEntity targetID='ldap' entityName='member'/>
</psp:calcRequest>
<psp:calcResponse >
<psp:id ID='test.subject.1'/>
<psp:pso entityName='member'>
<psoID ID='uid=test.subject.1,ou=people,dc=example,dc=edu' targetID='ldap'/>
</psp:pso>
</psp:calcResponse>
|
In the psp examples which target ldap directories, the member dn is either retrieved via an ldap grouper subject lookup or via the grouper subject source cache.
After resolving reference identifiers, a calc response is returned by the psp for the calc request for the principal whose name is the change log sequence number :
| Code Block | ||||
|---|---|---|---|---|
| ||||
<psp:calcRequest returnData='everything'>
<psp:id ID='change_log_sequence_number:344'/>
</psp:calcRequest>
<psp:calcResponse >
<psp:id ID='change_log_sequence_number:344'/>
<psp:pso entityName='groupMembership'>
<psoID ID='cn=groupA,ou=edu,ou=groups,dc=example,dc=edu' targetID='ldap'/>
<capabilityData ... >
<spmlref:reference typeOfReference='member' ...>
<spmlref:toPsoID ID='uid=test.subject.1,ou=people,dc=example,dc=edu' targetID='ldap'/>
</spmlref:reference>
</capabilityData>
</psp:pso>
<psp:pso entityName='memberMembership'>
<psoID ID='uid=test.subject.1,ou=people,dc=example,dc=edu' targetID='ldap'/>
<capabilityData ... >
<spmlref:reference typeOfReference='memberOf' ... >
<spmlref:toPsoID ID='cn=groupA,ou=edu,ou=groups,dc=example,dc=edu' targetID='ldap'/>
</spmlref:reference>
</capabilityData>
</psp:pso>
</psp:calcResponse>
|
The calc response returned by the psp represents how an add or delete membership change log entry should be provisioned.foo
Real-Time Provisioning Beta-Testing : Grouper Subject Sources
...