Trapping a Java exception in the authentication flow for V3

[Wessel, Keith]

Hi, all,

When I log into my V3 IDP with a trailing slash on my username (don't' ask why I would do this, ask the user who found the bug), I get the following Java exception displayed a the bottom of the IDP error template page:

java.lang.IllegalArgumentException: Empty nameString not allowed

This is using Kerberos as my password authentication back-end. The error makes sense to me, but it wouldn't make any sense to an end user. Is there some way I can trpa this and map it to a user-friendly error message?

Thanks,
Keith