|
|
|
[
Permlink
| « Hide
]
Daniel Ostermeier - 29/Aug/08 12:00 AM
resolved in revision 4379
Several people have complained about this issue on our installation (2.0.38), so I do not think it's fixed. The backtrace looks almost exactly the same:
1: 10/7/09 12:21:52 PM CEST (5 secs ago) failure severe count :: 1 org.mortbay.jetty.servlet.ServletHandler :: handle 2: 3: /j_acegi_security_check: 4: 5: java.lang.IllegalArgumentException: [Assertion failed] - this String argument must have length; it cannot be <code>null</code> or empty 6: at org.springframework.util.Assert.hasLength(Assert.java:136) 7: at org.springframework.util.Assert.hasLength(Assert.java:147) 8: at org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices.loginSuccess(TokenBasedRememberMeServices.java:269) 9: at org.acegisecurity.ui.AbstractProcessingFilter.successfulAuthentication(AbstractProcessingFilter.java:389) 10: at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:211) 11: at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:274) 12: at org.acegisecurity.util.FilterChainProxy.doFilter(FilterChainProxy.java:148) 13: at org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:90) 14: at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) 15: at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118) 16: at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52) 17: at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) 18: at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:195) 19: at com.zutubi.pulse.servercore.spring.FilterWrapper.doFilter(FilterWrapper.java:46) 20: at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) 21: at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471) 22: at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568) 23: at org.mortbay.http.HttpContext.handle(HttpContext.java:1530) 24: at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633) 25: at org.mortbay.http.HttpContext.handle(HttpContext.java:1482) 26: at org.mortbay.http.HttpServer.service(HttpServer.java:909) 27: at org.mortbay.http.HttpConnection.service(HttpConnection.java:820) 28: at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986) 29: at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837) 30: at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:245) 31: at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) 32: at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) 33: ) Hi Rohan,
Are you able to check the configuration of one of the users that have seen this problem for me? In $PULSE_DATA/records/snapshot/users/<login>/record.xml, is there a a non-empty <value name="password">? (Don't include the value here for obvious reasons.) LDAP users should have randomly-generated (and regularly-changing) passwords that we use to allow remember me logins without storing the LDAP passwords at all (otherwise they would need to be stored in plain text, which we are not willing to do). I checked accounts of people who have seen this problem, and for them there's no "password" value at all. Other accounts which do have a "password" value (because they were created before we switched to using LDAP) don't see the problem.
When I create LDAP users I leave the password field blank, should I not do that? Hi Rohan,
No, what you have done is fine, it looks like Pulse is not generating the random password when it should. I have already checked over the code to make sure it looks reasonable, I'll now try to break it in practice and see if I can get into the same situation that you have. |
|||||||||||||||||||||||||||||||||||||||||||||||