COmanage Users List

[Nick Evangelou <>]

Hello Benn,

When I run the enrollment with CO Person/CO Person Role attributes, in the 
"Collect Petitioner Attributes" form the fields are not field with 
environment values (as it should be?).

In "Organizational Identity Source Records” there is an “Attached Identity”, 
and I think I spotted the error. The name attributes are null.

So, is there a way to create a CoPerson with the environment variables of an 
orgIdentity using the EnvSource Plugin?

Thank you,
Nick



> On 1 Jun 2018, at 02:53, Benn Oshrin 
> <>
>  wrote:
> 
> Hi Nick,
> 
> After the enrollment, is there an Org Identity attached to the CO Person
> record? If so, is the expected ePUID present in the Org Identity?
> 
> Also, in the CO Petition record created from the enrollment, is there an
> entry for "Organizational Identity Source Records" under "Attached
> Identities"?
> 
> Thanks,
> 
> -Benn-
> 
> On 5/30/18 10:04 AM, Nick Evangelou wrote:
>> Hello everyone,
>> 
>> I’m trying to create an enrollment flow to signup user. As known, in
>> Registry 4.0.0 CMP enrollment attributes will be removed, so I’m using
>> env Source to retrieve environment variables as described
>> here: 
>> https://spaces.internet2.edu/display/COmanage/Consuming+External+Attributes+via+Web+Server+Environment+Variables#ConsumingExternalAttributesviaWebServerEnvironmentVariables-SelfSignup
>> 
>> I execute all the steps as mentioned. 
>> In step 1d I set the following attributes:
>> 
>>    Identifier: eduPersonUniqueId
>>    Given Name (Official): givenName
>>    Family Name (Official): sn
>>    Identifier (ePUID): eduPersonUniqueId (marked as login)
>>    Email (Official): mail
>>    Affiliation: eduPersonPrimaryAffiliation
>>    Organisation: schacHomeOrganization
>> 
>> 
>> In step 3 I create the following attributes:
>> 
>>    Name (Official, CO Person)
>>    Email (Official, CO Person)
>>    Affiliation (CO Person Role)
>>    Valid From (CO Person Role)
>>    Valid Through (CO Person Role)
>> 
>> 
>> After running the enrollment flow a message pops up that to user isn’t
>> associated with a coPerson and should contact the admin to resolve this.
>> I have tried to turn of amp enrollment attributes and try again, but
>> nothing changed.
>> 
>> Could you provide me with more info or spot my mistake in this process?
>> 
>> Regards,
>> Nick