COmanage Users List

[Scott Koranda <>]

Hi Paul,

I will need to look in detail at the GrouperProvisioner to answer your
questions in detail. 

I should be able to get to that next week.

If this is an emergency please ping me directly.

Thanks,

Scott K

> Hi-
> 
> When manually adding a user via the API, we first create a new OrgId, then 
> a new COPerson.  We then proceed to link the two, add attributes, generate 
> identifiers, etc.
> 
> But, it is currently dying at the second step: adding a new COPerson, which 
> is a very simple API call that we've done many times before.
> 
> The first error in the log is this:
> 
> "Error: GrouperProvisioner provisioning action PA is not implemented"
> 
> ...followed by:
> "Error: GrouperProvisioner is unable to compute the Grouper subject for 
> coPersonId = 24534"
> 
> I suspect it is because the managed identifiers created by COmanage haven't 
> yet been generated during this process and so there's no way to provision 
> to Grouper.
> 
> But, best I can tell provisioning shouldn't be happening yet when just 
> adding a new CO Person (according to 
> https://spaces.at.internet2.edu/display/COmanage/Grouper+Provisioning+Plugin).
> 
> I also see an option to disable provisioning temporarily mentioned here: 
> https://spaces.at.internet2.edu/display/COmanage/Provisioning+From+Registry#ProvisioningFromRegistry-AboutProvisioning
> 
>                                 "Note for Developers
> 
> Provisioning can be disabled on a per model/save basis by passing the 
> option "provision" => false (v1.0.1 and later)."
> 
> ...but I see no examples for how to use it and when I try things don't go 
> well.
> 
> Any ideas other than temporarily disabling the GrouperProvisioner?
> 
> 
> 
> Thanks!
> -Paul