COmanage Users List

[Mike Manske <>]

cool ty - but when I set Petitioner Enrollment Authorization to
"Authenticated User" and "save" I get an error - "This field cannot be
left blank". Other values of the drop down do work... just not that
one.
Michael A. Manske
Leonard E. Parker Center for Gravitation, Cosmology and Astrophysics
University of Wisconsin - Milwaukee
KIRC 4198


On Wed, Apr 13, 2016 at 5:28 PM, Benn Oshrin 
<>
 wrote:
> I think you need to set Enrollment Authorization to "Authenticated User"
> instead of "None". (It was previously ambiguously determined by looking
> at some other configuration setting.)
>
> It doesn't look like we documented this as part of the upgrading
> instructions (or at all, really)... I'll fix that.
>
> BTW the behavior for automatically collecting eppn from $REMOTE_USER
> remains the same -- that's still determined by "Require Confirmation of
> Email" and "Require Enrollee Authentication" both being enabled. (Though
> if you populate it via an env variable that would work too.)
>
> Thanks,
>
> -Benn-
>
> On 4/13/16 5:18 PM, Mike Manske wrote:
>> upgraded to 9.4 and enrollment flows are working differently. We have
>> a self-signup flow that requires approval for enrollment, Enrollment
>> Authorization is set to 'none'.
>>
>> Previously, when a user navigated to the enrollment form, they would
>> be directed to authenticate first (we use shib), and session values
>> would be used to pre-populate the enrollment form.
>>
>> As of 9.4, users are not required to authenticate before the
>> enrollment form, and no values are pre-populated.
>>
>> Is this the behavior described at,
>> https://spaces.internet2.edu/display/COmanage/Upgrading+Registry+to+v0.9.4
>> specifically the line "CO Petitions are now created after the start
>> step of an enrollment flow, but before any attributes are collected.
>> "?
>>
>> To test, I ran an enrollment, manually entering all values, including
>> eppn. It worked. This would be ok I guess except for users who cannot
>> figure out their eppn (like google users).
>>
>> Thoughts?
>> Michael A. Manske
>>