I meet the same problem.
I checked the cookie directly,it seems that the email was saved correctly in cookie.But when been fetched by the identity for displaying, the email has been truncated.
It seems to be a bug.
Warting for the solution.
I have already faced this problem with a non-Seam application. It seems to be a browser specific issue. I think it is related to FireFox 3, since I didn't have it on earlier FireFox versions (but I may be wrong...). Anyway, I simply solved it in the none-Seam application by replacing the @ with ~ . Is there a workaround for this problem in Seam? Is it a reported bug?
I don't think so.
I get the same problem both in ie/Firefox2/Firefox3.
Other browsers haven't been checked yet.
Besides,I have told that the email saved in cookie is correct.
I'm using SEAM 2.0.2SP1.
I have the same question.
Anything new with this issue?
you guys arent leaving jsf commented out in your xhtml files are you? the interpreter will instantiate things within a comment. it has bit me several times in project i am currently working on..... including but not limited to... over writing my passwords in entity object.
you means i should remove all the
<!-- comment -->in the jsf file?
Althought I removed all the
commentin the page, the bug is still there.
Waiting for the official reply.
I can't reproduce this. I tested with the Seamspace example, using firstname.lastname@example.org as the username, and the cookie was persisted correctly, and also read back correctly into the Identity component. I'm using Firefox 3.
Oh and I should add that I'm also using latest SVN version of Seam. You may wish to try with the same version and see if the issue is still occurring.
I just put the latest version of Seam and it still doesn't work.
This is a weird problem, obviously it is not related to Seam but to the cookie mechanism.
I a non-Seam application that I have it just
startedhappening one day about a month ago. I cannot point out what was changed that caused this behavior. It becomes weirder: when I put the non-Seam application in production, it all works well and cookie information is fetched correctly.
Currently the only think I can thing of is that the Antivirus/Firewall (Bitdefender) may be blocking things there, but it seams like a weak assumption... let me know (the others that have this problem) if you are also using Bitdefender... ;-)
Some other thing I wanted to know about this rememberMe feature: Shouldn't it automatically login the user? I go to login screen, put my details and login. Then I take down the webapp and raise it again. It doesn't do autologin. When I go back to the login screen I see the
usernamefield filled automatically.
Is there a way of making autologin in Seam (assuming the
rememberMeshouldn't do it of course) ?
The auto-login feature will only be available in Seam 2.1.0 (where it is still not a recommended practice due to the possibility of XSS attacks).
Is this feature already implemented in 2.1.0 (I am trying it now)?
I have tried this with firefox3.0,the bug is still there.
I will try the
Anything came up the Seamspace example?