COmanage Developers List

[Benn Oshrin <>]

I think we need to see why this is failing do make any more progress. It
would be helpful to have a specific error message from the LDAP server
("not just the "Type or value exists" that is being returned to the
provisioner).

If you can't get that, then you could do the following

(1) Provision with only one role.
(2) Copy the LDAP record.
(3) Add the second role and delete the first.
(4) Copy the updated LDAP record.

We can then analyze the two records to try to reproduce the failure.

Thanks,

-Benn-

On 9/4/14 4:35 PM, Michael Manske (JIRA) wrote:
> 
>     [ 
> https://bugs.internet2.edu/jira/browse/CO-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19763#comment-19763
>  ] 
> 
> Michael Manske commented on CO-941:
> -----------------------------------
> 
> When I add a new role with a different affiliation, and a different title, 
> it still fails. Furthermore, since it is legitimate that a person may have 
> one affiliation with one COU, and a different affiliation with another, how 
> is this represented in the LDAP output?
> 
>> Multiple Roles for User Causes Provisioning to Fail
>> ---------------------------------------------------
>>
>>                 Key: CO-941
>>                 URL: https://bugs.internet2.edu/jira/browse/CO-941
>>             Project: COmanage
>>          Issue Type: Bug
>>          Components: Registry Plugins
>>    Affects Versions: COmanage Registry 0.9 (Essential Enneagon)
>>         Environment: dev 17d95f200af6c7b78e03ccba1ae1fdb0a9adc2cb
>>            Reporter: Michael Manske
>>            Assignee: Benn Oshrin
>>            Priority: Major
>>             Fix For: COmanage Registry 0.9.1 (Essential Enneagon Plus One)
>>
>>
>> Using LDAP Provisioning.
>> 1 - Enrolled and approved a user. Checked LDAP and confirmed provisioning 
>> took place. 
>> 2 - Edited Person record in CM for same. Added a new Role, with different 
>> COU.
>> 3 - Received notification that provisioning failed. Attempted to manually 
>> provision user, and got response 'Provisioning failed: Type or value 
>> exists (500)'.
>> The LDAP attribute eduPersonAffiliation comes from the Role affiliation, 
>> so it looks like it fails when there are more than one.
>> This is important to us because our users will belong to multiple COUs 
>> with different capacities.
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v6.2#6252)
>