myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manfred Geiler" <manfred.gei...@gmail.com>
Subject Re: [tobago] Problems with (jsf-)FormBasedLogin, stored passwords and FF
Date Mon, 19 Nov 2007 09:41:48 GMT
I use straight html input tags for my form based login pages.
Why do you need <h:input* for this? Because of skinning?
Rather than adding an intrusive "name" attribute I suggest to launch
two new components <tc:inputFormBasedUsername> and
<tc:inputFormBasedPassword>. The form based login is a very special
case and under normal circumstances overriding the name attribute for
a jsf input breaks everything. So this use case actually demands new
component types rather than a hack/patch in the standard input
component.

--Manfred


On Nov 19, 2007 10:24 AM, Volker Weber <v.weber@inexso.de> wrote:
> Hi,
>
> a problem which was noticed by me (on a linux FF) a while ago seems
> now also occuring on windows FF.
>
> We have a application with form based login where the loginpage is
> created by tobago.
> The name attribute of name and password fields are changed by
> javascript from the jsf-clientIds to the required
> "j_username"/"j_password" in onload.
>
> But this seems to late for the recognition of stored passwords in new FFs.
>
> My proposal is a new attribute "name" on tc:in which value (if exists)
> could be used as name attribute for the correspondending <input> tag
> instead of the clientId.
>
> Any objections or other ideas how to solve this?
>
>
> Regards,
>     Volker
>



-- 
http://www.irian.at
Your JSF powerhouse - JSF Consulting,
Development and Courses in English and
German

Professional Support for Apache MyFaces

Mime
View raw message