COmanage Users List

[Benn Oshrin <>]

On 3/27/14 1:24 PM, Niels van Dijk wrote:
> The following fields must be defined:
> (a)    COU, if COUs are enabled
> (b)    Org Identity Name (see note below)
> (c)    Org Identity Email Address
> (d)    CO Person Name (see note below)
> (e)    CO Person Role Affiliation
> (f)    See also the note below about automatically populating ePPN (no
> need to explicitly define an attribute for this)
> (g)    See also Configuring Registry Identifier Assignment (no need to
> explicitly define an attribute for this)
> (h)    See also Registry Platform Configuration

> 4) I have defined "CO Enrollment Attributes"
> Name            Name (Official, CO Person)      2 (requirement d)
> Affiliation     Affiliation (CO Person Role)    3 (requirement e)
> Your group      COU (CO Person Role)            1 (requirement a)
> I am assuming Org Identity Name and Org Identity Email Address will be
> set when the user authenticates. And I am assuming I do not need to
> configure these in the enrollemtn flow as attributes explicitly, as
> suggested by "Email Verification and Authentication"
>
> When I now start an enrollment, I am again greeted by "Not impemented",
> so I am still missing something, or have configured soemthing
> incorrectly. Any tips?

You need to explicitly define the attributes that you are assuming would 
be set (requirements b and c). These will be prepopulated using 
attributes from the IdP when the enrollment form renders (assuming 
everything else is set up correctly).

The documentation you refer to only says that the authenticated 
identifier will be attached to the org identity (corresponding to 
requirement f), not the name or email address (b and c).

Thanks,

-Benn-