Providing a custom UnknownUsername message with a ldap directAuthenticator

Max Spicer max.spicer at
Wed Jun 21 08:06:28 UTC 2023

We do have a chain of validators and they will be returning different
events so that is certainly possible.

In passing, I've also realised that the logic in our login-error.vm is also
failing to deal with the fact that we have multiple validators that can
return classified errors. We're just
using getClassifiedErrors().iterator().next() as per the sample so
presumably are only looking at the first error. In practice I doubt this
matters as we generally only return a generic "your username or password is
incorrect" message.



On Wed, 21 Jun 2023 at 02:08, Cantor, Scott <cantor.2 at> wrote:

> I don't think this is your problem (specifically because using the "whole"
> string seemed to work), but there is a bug in the released version(s) that
> causes problems when chains of validators all signal different events.
> It generally affects auditing more than anything else but I guess it's
> possible things are stepping on each other in other areas.
> -- Scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the users mailing list