Skip to Content.
Sympa Menu

comanage-users - Re: [comanage-users] enrollment flow in 9.4

Subject: COmanage Users List

List archive

Re: [comanage-users] enrollment flow in 9.4

Chronological Thread 
  • From: Benn Oshrin <>
  • To:
  • Subject: Re: [comanage-users] enrollment flow in 9.4
  • Date: Wed, 13 Apr 2016 18:28:48 -0400

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.)



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,
> 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

Archive powered by MHonArc 2.6.16.

Top of Page