COmanage Developers List

[Benn Oshrin <>]

As a general note, if you still see errors after we "resolve" a ticket, 
feel free to reopen it (or cut a new one, as appropriate).

Thanks,

-Benn-


-------- Forwarded Message --------
Subject: [JIRA] (CO-1044) Subject cannot join multiple COs
Date: Sat, 9 May 2015 15:59:01 +0000
From: Benn Oshrin (JIRA) 
<>
To: 



    [ 
https://bugs.internet2.edu/jira/browse/CO-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21401#comment-21401 
]

Benn Oshrin commented on CO-1044:
---------------------------------

This should now be fixed for pool_org_identities=false.

> Subject cannot join multiple COs
> --------------------------------
>
>                 Key: CO-1044
>                 URL: https://bugs.internet2.edu/jira/browse/CO-1044
>             Project: COmanage
>          Issue Type: Bug
>          Components: Registry
>    Affects Versions: COmanage Registry 0.9.3 (Essential Enneagon Plus Plus 
> Plus)
>         Environment: Debian 7.8 MySQL 5.5.41-0+wheezy1
>            Reporter: Michael Manske
>            Assignee: Benn Oshrin
>            Priority: Critical
>             Fix For: COmanage Registry 0.9.4 (EEP4)
>
>         Attachments: cmEnrollDetail.xls, cmEnrollHdr.xls
>
>
> cm_cmp_enrollment_configurations.pool_org_identities (Pool Organizational 
> Identities) is FALSE
> 2 COs, each which self enrollment flows, basically identical.  Details 
> attached.
> Subject complete enrollment form for first CO, confirmed email, and was 
> approved.
> Same subject then completed enrollment form for second CO, received email with 
> invitation to confirm, navigated to link, selected 'Accept' link (tab-like button 
> in top-left of content area). Error returned with message 'Identifier <eppn> 
> already in use.'
> The petition is left at 'Pending Confirmation'.
> Other details, which may or may not be relevant.
> Looking at the database, in table cm_identifiers, there is only a single 
> record for the eppn in question, and that has an org_identity_id value. This 
> was a result of the first enrollment. In previous versions of COmanage, there 
> would have been two records for the eppn, one with an  org_identity_id value 
> and one with a co_person_id value.



--
This message was sent by Atlassian JIRA
(v6.2#6252)