Event transition issue for IdP 3.3.1

O'Dowd, Josh Josh.O'Dowd at mso.umt.edu
Thu Apr 13 11:11:00 EDT 2017


We went from 3.2 to 3.3.0, though admittedly, I skimmed the notes and missed that.  You and I did work through some issues with c14n and the expiring-password condition flow when we ran into that in the 3.3.0 upgrade.  The manual workaround that I had put in place is still there.  I just posted more details prior to this post, on that.  I think it all ties in, and I need to clean that up to account for fixes that came in 3.3.1.

Josh
________________________________________
From: users [users-bounces at shibboleth.net] on behalf of Cantor, Scott [cantor.2 at osu.edu]
Sent: Thursday, April 13, 2017 8:53 AM
To: Shib Users
Subject: RE: Event transition issue for IdP 3.3.1

> I noticed the 3.3.1 release notes and we did add transitions to authn-events-
> flow.xml and intercept-events-flow.xml, to account for some custom events
> we have in place, but this appears to be for a native event.  Do I need a
> transition somewhere for this as well?

Earlier in the release notes, there was a more serious regression introduced in 3.3.0 that only impacts people using those condition hooks, it's highlighted there. Arguably I should have repeated it in 3.3.1 notes, I'll add a pointer on it now.

Essentially you must have gone from 3.2 to 3.3.1 or you'd have hit it earlier.

-- Scott

--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net


More information about the users mailing list