Modifying Login Flows

[Cantor, Scott]

(This title by the way is not a great description of what's going in here. You do *not* modify login flows, that's not supported.)

On 1/24/19, 6:39 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:

<some ideas>

I think the simplest option that's the least invasive to the existing view is actually a combination of what I suggested. What I would probably do (well, aside from the defaults and just letting it be) is to map the relevant error messages to a custom Event name that doesn't match one of the "known" events.

Instead of ExpiredPassword, map the error strings to MyExpiredPassword or CustomExpiredPassword or whatever, and follow the documentation in [1] under Custom Events. That describes how to get your custom event to complete the flows gracefully and then head over to the error handling docs to do what I suggested and set up a template to handle it.

That's simpler in the end because it's less invasive to the login view, which is already complex enough, and isn't really meant to be handling errors that way.

I'd forgotten this was already outlined in the top level docs. I'll link it more contextually into some of the other pages.

-- Scott

[1] https://wiki.shibboleth.net/confluence/display/IDP30/AuthenticationConfiguration