Modifying Login Flows

[Cantor, Scott]

On 1/29/19, 7:44 PM, "users on behalf of Mr. Christopher Bland" <users-bounces at shibboleth.net on behalf of chris at fdu.edu> wrote:
> I am clearly missing something. 

"FDUExpiredPassword" and "FDUChangePassword" aren't the same string, and not the same event. That doesn't line up.

But I think you're correct that for this to work you have to add a transition in conditions-flow.xml to map whichever of those two events you really want to be using to itself as a state transition. The system is designed to trap every event on the login form because I can't really understand how it makes sense to do anything else. Every system I've ever used works that way.

But if you want to really fail out, you'd have to add <transition on=" FDUExpiredPassword " to=" FDUExpiredPassword " /> to the ValidateUsernamePassword action-state in that file so it will go ahead and forward out that event. The other changes should be sufficient to make that bubble out the rest of the way. But the event names do have to line up everywhere, you can't use one in the message mapping bean and another in the rest of the changes.

-- Scott