Re: [Wicket-user] Authentication and page expired
On 4/25/07, Xavier Hanin [EMAIL PROTECTED] wrote: On 4/25/07, Igor Vaynberg [EMAIL PROTECTED] wrote: what do you mean by once authenticated what does your loginpage code look like, eg how do you navigate back? My login page is really very simple, it doesn't do much except include a SigninPanel. So as far as I understand from the SigninPanel code, the navigation back is handled by Component#continueToOriginalDestination(). But maybe I'd need to implement something special in my LoginPage, and not rely on the SigninPanel only? After some modifications in the code, the problem disappears if I use a BookmarkablePageLink instead of a PageLink. But I'd still would like to know if there is a way to avoid this problem with a simple PageLink being intercepted by an authentication... and for the moment I still don't know. Xavier - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Authentication and page expired
hrm. it does seem rather strange. we have a similar authenetication stuff going on in a few projects and it works. but i wonder is the page being intercepted a stateless page? is the login page a stateless page? -igor On 4/26/07, Xavier Hanin [EMAIL PROTECTED] wrote: On 4/25/07, Xavier Hanin [EMAIL PROTECTED] wrote: On 4/25/07, Igor Vaynberg [EMAIL PROTECTED] wrote: what do you mean by once authenticated what does your loginpage code look like, eg how do you navigate back? My login page is really very simple, it doesn't do much except include a SigninPanel. So as far as I understand from the SigninPanel code, the navigation back is handled by Component#continueToOriginalDestination(). But maybe I'd need to implement something special in my LoginPage, and not rely on the SigninPanel only? After some modifications in the code, the problem disappears if I use a BookmarkablePageLink instead of a PageLink. But I'd still would like to know if there is a way to avoid this problem with a simple PageLink being intercepted by an authentication... and for the moment I still don't know. Xavier - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Authentication and page expired
On 4/26/07, Igor Vaynberg [EMAIL PROTECTED] wrote: hrm. it does seem rather strange. we have a similar authenetication stuff going on in a few projects and it works. but i wonder is the page being intercepted a stateless page? is the login page a stateless page? I don't think so, because I haven't done anything special, but I don't know wicket well enough to say. But if you say it should be working, I will double check on my own, check again the examples, and see if I can figure out what's going on, and come back with more details if I'm really lost. Thanks for your help. Xavier -igor On 4/26/07, Xavier Hanin [EMAIL PROTECTED] wrote: On 4/25/07, Xavier Hanin [EMAIL PROTECTED] wrote: On 4/25/07, Igor Vaynberg [EMAIL PROTECTED] wrote: what do you mean by once authenticated what does your loginpage code look like, eg how do you navigate back? My login page is really very simple, it doesn't do much except include a SigninPanel. So as far as I understand from the SigninPanel code, the navigation back is handled by Component#continueToOriginalDestination(). But maybe I'd need to implement something special in my LoginPage, and not rely on the SigninPanel only? After some modifications in the code, the problem disappears if I use a BookmarkablePageLink instead of a PageLink. But I'd still would like to know if there is a way to avoid this problem with a simple PageLink being intercepted by an authentication... and for the moment I still don't know. Xavier - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- Learn Ivy at ApacheCon: http://www.eu.apachecon.com/ Manage your dependencies with Ivy! http://incubator.apache.org/ivy/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Authentication and page expired
I'm sorry, I've just noticed that I have an exception[1] before getting the Page Expired message. The exception occurs during deserialization of the page from which I come, and is related to a field injected with via Spring using the wicket-spring-annot. Then this exception is catched and simply output with a e.printStackTrace() (nothing in the log, see org.apache.wicket.util.lang.Objects.byteArrayToObject) which then results in a NPE in FilePageStore logged at debug level, which results in a null page in AbstractRequestCycleProcessor.resolveRenderedPage, which throws the PageExpiredException. So I have two questions: - is it normal that a deserialization exception is not more verbose (a printstacktrace + a not directly related debug message only)? - how can I deal with my spring injected field? Do I have to write specific serialization/deserialization code, to reinject the field at deserialization time? Isn't this case of serializing a component with spring injected fields pretty common? Ok, it's more than two questions :-) Xavier [1] org.apache.wicket.util.io.WicketSerializeableException: Error reading field: projects for object class: class org.xoocode.xooctory.web.projects.ProjectsPage NOTE: if you feel Wicket is at fault with this exception, please report to the mailing list. You can switch to JDK based serialization by calling: org.apache.wicket.util.lang.Objects.setObjectStreamFactory(new IObjectStreamFactory.DefaultObjectStreamFactory()) e.g. in the init method of your application at org.apache.wicket.util.io.ClassStreamHandler.readFields(ClassStreamHandler.java:426) at org.apache.wicket.util.io.WicketObjectInputStream.readObjectOverride(WicketObjectInputStream.java:97) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:345) at org.apache.wicket.util.lang.Objects.byteArrayToObject(Objects.java:397) at org.apache.wicket.protocol.http.FilePageStore.getPage(FilePageStore.java:476) at org.apache.wicket.protocol.http.SecondLevelCacheSessionStore$SecondLevelCachePageMap.get(SecondLevelCacheSessionStore.java:137) at org.apache.wicket.Session.getPage(Session.java:741) at org.apache.wicket.request.AbstractRequestCycleProcessor.resolveRenderedPage(AbstractRequestCycleProcessor.java:427) at org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:137) at org.apache.wicket.RequestCycle.step(RequestCycle.java:1026) at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1127) at org.apache.wicket.RequestCycle.request(RequestCycle.java:489) at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:248) at org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:126) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:367) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:285) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:457) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:751) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:500) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:357) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:329) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475) Caused by: java.lang.NullPointerException at org.apache.wicket.util.io.ClassStreamHandler.createObject(ClassStreamHandler.java:303) at org.apache.wicket.util.io.WicketObjectInputStream.readObjectOverride(WicketObjectInputStream.java:92) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:345) at org.apache.wicket.util.io.ClassStreamHandler$ObjectFieldAndIndex.readField(ClassStreamHandler.java:871) at org.apache.wicket.util.io.ClassStreamHandler.readFields(ClassStreamHandler.java:416) ... 30 more On 4/26/07, Xavier Hanin [EMAIL PROTECTED] wrote: On 4/26/07, Igor Vaynberg [EMAIL PROTECTED] wrote: hrm. it does seem rather strange. we have a similar authenetication stuff going on in a few projects and it works. but i
Re: [Wicket-user] Authentication and page expired
ah well that explains it :) 1.3 is using our experimental serialization code to save the state which results in a much smaller size then the default serialization. currently it doesnt handle all cases, such as serializing proxies. that is why there are instructions in that error message that tell you how to switch to default serialization. once you do that everything should work. -igor On 4/26/07, Xavier Hanin [EMAIL PROTECTED] wrote: I'm sorry, I've just noticed that I have an exception[1] before getting the Page Expired message. The exception occurs during deserialization of the page from which I come, and is related to a field injected with via Spring using the wicket-spring-annot. Then this exception is catched and simply output with a e.printStackTrace() (nothing in the log, see org.apache.wicket.util.lang.Objects.byteArrayToObject) which then results in a NPE in FilePageStore logged at debug level, which results in a null page in AbstractRequestCycleProcessor.resolveRenderedPage, which throws the PageExpiredException. So I have two questions: - is it normal that a deserialization exception is not more verbose (a printstacktrace + a not directly related debug message only)? - how can I deal with my spring injected field? Do I have to write specific serialization/deserialization code, to reinject the field at deserialization time? Isn't this case of serializing a component with spring injected fields pretty common? Ok, it's more than two questions :-) Xavier [1] org.apache.wicket.util.io.WicketSerializeableException: Error reading field: projects for object class: class org.xoocode.xooctory.web.projects.ProjectsPage NOTE: if you feel Wicket is at fault with this exception, please report to the mailing list. You can switch to JDK based serialization by calling: org.apache.wicket.util.lang.Objects.setObjectStreamFactory(new IObjectStreamFactory.DefaultObjectStreamFactory()) e.g. in the init method of your application at org.apache.wicket.util.io.ClassStreamHandler.readFields( ClassStreamHandler.java:426) at org.apache.wicket.util.io.WicketObjectInputStream.readObjectOverride( WicketObjectInputStream.java:97) at java.io.ObjectInputStream.readObject(ObjectInputStream.java :345) at org.apache.wicket.util.lang.Objects.byteArrayToObject( Objects.java:397) at org.apache.wicket.protocol.http.FilePageStore.getPage( FilePageStore.java:476) at org.apache.wicket.protocol.http.SecondLevelCacheSessionStore$SecondLevelCachePageMap.get (SecondLevelCacheSessionStore.java:137) at org.apache.wicket.Session.getPage(Session.java:741) at org.apache.wicket.request.AbstractRequestCycleProcessor.resolveRenderedPage (AbstractRequestCycleProcessor.java:427) at org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve( WebRequestCycleProcessor.java:137) at org.apache.wicket.RequestCycle.step(RequestCycle.java:1026) at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1127) at org.apache.wicket.RequestCycle.request(RequestCycle.java:489) at org.apache.wicket.protocol.http.WicketFilter.doGet( WicketFilter.java:248) at org.apache.wicket.protocol.http.WicketServlet.doGet( WicketServlet.java:126) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.mortbay.jetty.servlet.ServletHolder.handle( ServletHolder.java:491) at org.mortbay.jetty.servlet.ServletHandler.handle( ServletHandler.java:367) at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:185) at org.mortbay.jetty.servlet.SessionHandler.handle( SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle( ContextHandler.java:689) at org.mortbay.jetty.webapp.WebAppContext.handle( WebAppContext.java:391) at org.mortbay.jetty.handler.HandlerWrapper.handle( HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:285) at org.mortbay.jetty.HttpConnection.handleRequest( HttpConnection.java:457) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete( HttpConnection.java:751) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:500) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java :209) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java :357) at org.mortbay.io.nio.SelectChannelEndPoint.run( SelectChannelEndPoint.java:329) at org.mortbay.thread.BoundedThreadPool$PoolThread.run( BoundedThreadPool.java:475) Caused by: java.lang.NullPointerException at org.apache.wicket.util.io.ClassStreamHandler.createObject( ClassStreamHandler.java:303) at org.apache.wicket.util.io.WicketObjectInputStream.readObjectOverride( WicketObjectInputStream.java:92) at java.io.ObjectInputStream.readObject(ObjectInputStream.java :345) at
Re: [Wicket-user] Authentication and page expired
On 4/26/07, Igor Vaynberg [EMAIL PROTECTED] wrote: ah well that explains it :) 1.3 is using our experimental serialization code to save the state which results in a much smaller size then the default serialization. currently it doesnt handle all cases, such as serializing proxies. that is why there are instructions in that error message that tell you how to switch to default serialization. once you do that everything should work. Indeed, everything works now :-) I guess it's only because you are in development on this feature, but I think that this kind of problem is important enough to deserve either an exception going higher on the method call stack (maybe wrapping the IOException in a RuntimeException) or at least use the logging mechanism at warn or error level, instead of calling a simple printStackTrace, because it's not straightforward to figure out the cause of this Page Expired message. Anyway, thanks a lot for your help and your time. Xavier -igor On 4/26/07, Xavier Hanin [EMAIL PROTECTED] wrote: I'm sorry, I've just noticed that I have an exception[1] before getting the Page Expired message. The exception occurs during deserialization of the page from which I come, and is related to a field injected with via Spring using the wicket-spring-annot. Then this exception is catched and simply output with a e.printStackTrace() (nothing in the log, see org.apache.wicket.util.lang.Objects.byteArrayToObject) which then results in a NPE in FilePageStore logged at debug level, which results in a null page in AbstractRequestCycleProcessor.resolveRenderedPage, which throws the PageExpiredException. So I have two questions: - is it normal that a deserialization exception is not more verbose (a printstacktrace + a not directly related debug message only)? - how can I deal with my spring injected field? Do I have to write specific serialization/deserialization code, to reinject the field at deserialization time? Isn't this case of serializing a component with spring injected fields pretty common? Ok, it's more than two questions :-) Xavier [1] org.apache.wicket.util.io.WicketSerializeableException: Error reading field: projects for object class: class org.xoocode.xooctory.web.projects.ProjectsPage NOTE: if you feel Wicket is at fault with this exception, please report to the mailing list. You can switch to JDK based serialization by calling: org.apache.wicket.util.lang.Objects.setObjectStreamFactory (new IObjectStreamFactory.DefaultObjectStreamFactory()) e.g. in the init method of your application at org.apache.wicket.util.io.ClassStreamHandler.readFields(ClassStreamHandler.java:426) at org.apache.wicket.util.io.WicketObjectInputStream.readObjectOverride (WicketObjectInputStream.java:97) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:345) at org.apache.wicket.util.lang.Objects.byteArrayToObject(Objects.java:397) at org.apache.wicket.protocol.http.FilePageStore.getPage (FilePageStore.java:476) at org.apache.wicket.protocol.http.SecondLevelCacheSessionStore$SecondLevelCachePageMap.get(SecondLevelCacheSessionStore.java:137) at org.apache.wicket.Session.getPage(Session.java :741) at org.apache.wicket.request.AbstractRequestCycleProcessor.resolveRenderedPage(AbstractRequestCycleProcessor.java:427) at org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java :137) at org.apache.wicket.RequestCycle.step(RequestCycle.java:1026) at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1127) at org.apache.wicket.RequestCycle.request(RequestCycle.java :489) at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:248) at org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:126) at javax.servlet.http.HttpServlet.service (HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491) at org.mortbay.jetty.servlet.ServletHandler.handle (ServletHandler.java:367) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle (ContextHandler.java:689) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle (Server.java:285) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:457) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:751) at
Re: [Wicket-user] Authentication and page expired
well, at first i didnt want to believe we had a printstacktrace() somewhere. but yeah i found it. i changed it to throw an rte, hopefully there was a very good reason for swallowing it like that and someone will revert my change with an explanation. -igor On 4/26/07, Xavier Hanin [EMAIL PROTECTED] wrote: On 4/26/07, Igor Vaynberg [EMAIL PROTECTED] wrote: ah well that explains it :) 1.3 is using our experimental serialization code to save the state which results in a much smaller size then the default serialization. currently it doesnt handle all cases, such as serializing proxies. that is why there are instructions in that error message that tell you how to switch to default serialization. once you do that everything should work. Indeed, everything works now :-) I guess it's only because you are in development on this feature, but I think that this kind of problem is important enough to deserve either an exception going higher on the method call stack (maybe wrapping the IOException in a RuntimeException) or at least use the logging mechanism at warn or error level, instead of calling a simple printStackTrace, because it's not straightforward to figure out the cause of this Page Expired message. Anyway, thanks a lot for your help and your time. Xavier -igor On 4/26/07, Xavier Hanin [EMAIL PROTECTED] wrote: I'm sorry, I've just noticed that I have an exception[1] before getting the Page Expired message. The exception occurs during deserialization of the page from which I come, and is related to a field injected with via Spring using the wicket-spring-annot. Then this exception is catched and simply output with a e.printStackTrace() (nothing in the log, see org.apache.wicket.util.lang.Objects.byteArrayToObject) which then results in a NPE in FilePageStore logged at debug level, which results in a null page in AbstractRequestCycleProcessor.resolveRenderedPage, which throws the PageExpiredException. So I have two questions: - is it normal that a deserialization exception is not more verbose (a printstacktrace + a not directly related debug message only)? - how can I deal with my spring injected field? Do I have to write specific serialization/deserialization code, to reinject the field at deserialization time? Isn't this case of serializing a component with spring injected fields pretty common? Ok, it's more than two questions :-) Xavier [1] org.apache.wicket.util.io.WicketSerializeableException: Error reading field: projects for object class: class org.xoocode.xooctory.web.projects.ProjectsPage NOTE: if you feel Wicket is at fault with this exception, please report to the mailing list. You can switch to JDK based serialization by calling: org.apache.wicket.util.lang.Objects.setObjectStreamFactory (new IObjectStreamFactory.DefaultObjectStreamFactory()) e.g. in the init method of your application at org.apache.wicket.util.io.ClassStreamHandler.readFields( ClassStreamHandler.java:426) at org.apache.wicket.util.io.WicketObjectInputStream.readObjectOverride (WicketObjectInputStream.java:97) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:345) at org.apache.wicket.util.lang.Objects.byteArrayToObject(Objects.java:397) at org.apache.wicket.protocol.http.FilePageStore.getPage (FilePageStore.java:476) at org.apache.wicket.protocol.http.SecondLevelCacheSessionStore$SecondLevelCachePageMap.get (SecondLevelCacheSessionStore.java:137) at org.apache.wicket.Session.getPage(Session.java :741) at org.apache.wicket.request.AbstractRequestCycleProcessor.resolveRenderedPage (AbstractRequestCycleProcessor.java:427) at org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve( WebRequestCycleProcessor.java :137) at org.apache.wicket.RequestCycle.step(RequestCycle.java:1026) at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1127) at org.apache.wicket.RequestCycle.request(RequestCycle.java :489) at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java :248) at org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java :126) at javax.servlet.http.HttpServlet.service (HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491) at org.mortbay.jetty.servlet.ServletHandler.handle (ServletHandler.java:367) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java :185) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle (ContextHandler.java:689) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391) at
Re: [Wicket-user] Authentication and page expired
what do you mean by once authenticated
what does your loginpage code look like, eg how do you navigate back?
-igor
On 4/25/07, Xavier Hanin [EMAIL PROTECTED] wrote:
Hi,
I'm trying to implement authentication using wicket and I get some
trouble...
My problem is that when I try to access a page requiring
authentication, I get redirected to a login page. Fine. But then, once
authenticated, I get a Page expired message, and I don't find how to
get rid of it instead of going to the page requiring authentication.
Here is some detail on what I've done:
- I use the not yet released wicket 1.3.0-incubating-beta1 [1]
- I use wicket-auth-roles, with an AuthenticatedWebApplication,
AuthenticatedWebSession, and RoleAuthorizationStrategy
- my link to the role protected page is created like this:
new PageLink(project, new IPageLink() {
public Class getPageIdentity() {
return ProjectPage.class;
}
public Page getPage() {
return new ProjectPage(project);
}
}
- my page is protected with an annotation:
@AuthorizeInstantiation(Roles.USER)
public class ProjectCreationPage extends WebPage {
- my signin page is a very simple page using a panel including the
SignInPanel from wicket-auth-roles
Any idea?
Xavier
[1]
http://people.apache.org/~dashorst/releases/apache-wicket-1.3.0-incubating-beta1/m2-repo/
--
Learn Ivy at ApacheCon: http://www.eu.apachecon.com/
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Authentication and page expired
On 4/25/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
what do you mean by once authenticated
what does your loginpage code look like, eg how do you navigate back?
My login page is really very simple, it doesn't do much except include
a SigninPanel. So as far as I understand from the SigninPanel code,
the navigation back is handled by
Component#continueToOriginalDestination(). But maybe I'd need to
implement something special in my LoginPage, and not rely on the
SigninPanel only?
Xavier
-igor
On 4/25/07, Xavier Hanin [EMAIL PROTECTED] wrote:
Hi,
I'm trying to implement authentication using wicket and I get some
trouble...
My problem is that when I try to access a page requiring
authentication, I get redirected to a login page. Fine. But then, once
authenticated, I get a Page expired message, and I don't find how to
get rid of it instead of going to the page requiring authentication.
Here is some detail on what I've done:
- I use the not yet released wicket 1.3.0-incubating-beta1 [1]
- I use wicket-auth-roles, with an AuthenticatedWebApplication,
AuthenticatedWebSession, and RoleAuthorizationStrategy
- my link to the role protected page is created like this:
new PageLink(project, new IPageLink() {
public Class getPageIdentity() {
return ProjectPage.class;
}
public Page getPage() {
return new ProjectPage(project);
}
}
- my page is protected with an annotation:
@AuthorizeInstantiation(Roles.USER)
public class ProjectCreationPage extends WebPage {
- my signin page is a very simple page using a panel including the
SignInPanel from wicket-auth-roles
Any idea?
Xavier
[1]
http://people.apache.org/~dashorst/releases/apache-wicket-1.3.0-incubating-beta1/m2-repo/
--
Learn Ivy at ApacheCon: http://www.eu.apachecon.com/
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
--
Learn Ivy at ApacheCon: http://www.eu.apachecon.com/
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
