Trapping a Java exception in the authentication flow for V3

[Wessel, Keith]

If that's the case, and it seems like it is, were happy to wait for 3.2.0 to fix this.

Thanks,
Keith


-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Wednesday, October 28, 2015 3:16 PM
To: Shib Users <users at shibboleth.net>
Subject: Re: Trapping a Java exception in the authentication flow for V3

On 10/28/15, 4:14 PM, "users on behalf of Cantor, Scott" <users-bounces at shibboleth.net on behalf of cantor.2 at osu.edu> wrote:



>On 10/28/15, 4:03 PM, "users on behalf of Wessel, Keith" <users-bounces at shibboleth.net on behalf of kwessel at illinois.edu> wrote:
>
>
>
>>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?
>
>Is it displaying that when it redisplays the login form?

Also, if it's outright crashing because the exception is a runtime error and blowing the whole thing up, that probably will go away in the next version anyway, the Kerberos code was all replaced.

-- Scott

-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net