[prev in list] [next in list] [prev in thread] [next in thread] 

List:       forgerock-openam
Subject:    [OpenAM] Custom Authentication Module Error Messages
From:       majorpetya () sch ! bme ! hu (=?ISO-8859-1?Q?Major_P=E9ter?=)
Date:       2010-11-29 18:58:23
Message-ID: 4CF3F7CF.4060705 () sch ! bme ! hu
[Download RAW message or body]

Hi,

I think the LDAP module's xml is using something like this. It talks 
with the user through the header attribute, and that 'header' is just 
displayed on the login page.
I think AMLoginModule#substituteHeader is what you're looking for.
In your callbackdescriptor xml you need a callbacks tag something like this:
<Callbacks length="0" order="3" timeout="120" header="" error="true" />
But if you want somehow a back navigation support, then you need to do 
some magic, like create a confirmationcallback which will find in your 
code, which was the last state, and will move back to there.
Hope this helps

Regards,
Peter

2010-11-29 19:49 keltez?ssel, Jon Stockdill ?rta:
> I am still stuck on this one.  Can Callbacks be used for this
> functionality?  It seems like it might be the right way.
>
> --jon
>
>
> On Tue, Nov 23, 2010 at 11:13 PM, Jon Stockdill<jon.stockdill at gmail.com>  wrote:
>> I have successfully implemented AMLoginModule, but would like to
>> provide different messages than one "authFailed" message.  Reviewing
>> AMLoginContext, It seems like this is done by throwing
>> MessageLoginException, but it seems like the exceptions are being
>> wrapped in AMLoginModule.wrapProcess, so throwing
>> MessageLoginException will not work.
>>
>> What is the preferred method for providing custom exceptions/messages?
>>
>> Thanks for the help,
>>
>> --jon

[prev in list] [next in list] [prev in thread] [next in thread]