Login errors in V3 when using Kerberos authentication
Tom Zeller
tzeller at dragonacea.biz
Fri Aug 7 18:44:05 EDT 2015
> On Aug 7, 2015, at 5:27 PM, Tom Zeller <tzeller at dragonacea.biz> wrote:
>
>
>>> So, in other words, Tom, just check the contents of the message string in login-error.vm and display my own text if that's what's in it. That correct ?
>>
>> That’s what I’ve thought of so far.
>>
>>> I thought of this, but it sees to be against everything you all went for in V3. I'm okay with it, though.
>>
>> I don’t really like my suggestion either, but like I said, Scott will probably have a better one.
>
> If "Pre-authentication information was invalid (24)” equals invalid password, you can “classify” that error message in conf/auth/password-auth-config.xml” :
>
> <entry key="InvalidPassword”>
> <list>
> <value>InvalidCredentials</value>
> <value>PREAUTH_FAILED</value>
> <value>INVALID_CREDENTIALS</value>
> <value>Pre-authentication information was invalid (24)</value>
> </list>
> </entry>
And continuing, you could define a new message map in password-auth-config.xml, for example :
<entry key="MyMessage">
<list>
<value>Pre-authentication information was invalid (24)</value>
</list>
</entry>
and the corresponding message to be displayed in messages/authn-messages.properties, for example :
MyMessage = my-message
my-message.message = My Message
More information about the users
mailing list