AW: IDP 4.3.1 login.vm view - error messages?

[Käfer Thomas]

I've managed to solve the issue, by flipping the order in which Exceptions & ClassifiedErrors are processed in the `login-error.vm` Velocity template.

By default ClassifiedErrors are processed first, and only if none of those exists the Exceptions are read. Since our custom error messages are transported using Exceptions, we first process those, and only if none of them exists look onto the ClassifiedErrors, of which we ignore not only the $eventId ignored by default = "ReselectFlow" but also "NoCredentials" which is always existent in 4.3.1 when the login page is loaded first before the user tried entering any credentials.
________________________________
Von: Käfer Thomas <thomas.kaefer at fh-campuswien.ac.at>
Gesendet: Dienstag, 18. April 2023 12:35
An: Cantor, Scott <cantor.2 at osu.edu>; Shib Users <users at shibboleth.net>
Betreff: AW: IDP 4.3.1 login.vm view - error messages?

Hey there Scott,

thanks for the explanations!

Can you please point me to resources that explain how I can
> handle that event specially in the view

Thank you,
kind regards,
Thomas Käfer
________________________________
Von: Cantor, Scott <cantor.2 at osu.edu>
Gesendet: Dienstag, 11. April 2023 16:53
An: Käfer Thomas <thomas.kaefer at fh-campuswien.ac.at>; Shib Users <users at shibboleth.net>
Betreff: Re: IDP 4.3.1 login.vm view - error messages?

> Do you have any hint's how I could get back the behaviour from 4.2.1 and
> before where we only get an error message after a failed password login
> attempt and that one is the custom one thrown from our JAAS code like: throw
> new FailedLoginException(ourErrorMessage)?

No, that would take member support sorts of effort to dig into, I cannot do that for free.

What I can say is that the point of the fix was that before when an event got signaled that didn't have a mapping to a classified error, it just got dropped on the floor, but now if nothing has been captured it stores off the signalled event ID as the classified error. Your template is probably seeing that classified error event and reporting it, and that's what it is designed to do out of the box. If you don't want it to do that, you need to handle that event specially in the view.

What it actually displays hasn't changed, that depends on the event string being tied to a message key in the message file(s).

-- Scott



Informationen zum Datenschutz: www.fh-campuswien.ac.at/datenschutzerklaerung
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20230502/96d222ab/attachment.htm>