Re: Problem with wicket authentication

implicity and fewer code is my mantra!) > I had seen the Swarm one, but it didn't look as straightforward. Maybe I > will give it a try if I can't go with the standard one. > > Regards, > Hugues > - Regards, Hugues -- View this message in context: http://www.nabbl

Re: Problem with wicket authentication

t; >> > >> public final class LoginPage extends SignInPage { > >> } > >> > >> > >> And finally, the admin page to protect: > >> > >> @AuthorizeInstantiation("USER") > >> public class AdminPage extends WebPage { > >> } > >> > >> The problem is that a click from the HomePage always brings the > >> AdminPage, without any > >> LoginPage displayed. > >> > >> I used Wicket 1.3 beta4. > >> > >> After reading the Wicket example and 2 tutorials on authentication, I > >> really can't see what I'm missing. > >> Any idea ? > >> > >> Hugues > >> > >> > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > Quoted from: > http://www.nabble.com/Problem-with-wicket-authentication-tf4751663.html#a13602300 > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Problem with wicket authentication

Hugues Pichereau wrote: Sebastiaan van Erk wrote: [...] If you do override init, make sure to call super.init() Whao! well done, Sebastiaan, I was overriding init(), and not calling super.init(); Now it works. But what bugs me is that it solves my own application (where init() was override

Re: Problem with wicket authentication

", AdminPage.class)); >>} >> } >> >> >> LoginPage.html has: >> >> >> public final class LoginPage extends SignInPage { >> } >> >> >> And finally, the admin page to protect: >> >> @AuthorizeInstantiat

Re: Problem with wicket authentication

without any > LoginPage displayed. > > I used Wicket 1.3 beta4. > > After reading the Wicket example and 2 tutorials on authentication, I > really can't see what I'm missing. > Any idea ? > > Hugues > > > -- View this message in context: http://www.nabble.com/Problem-with-wicket-authentication-tf4751663.html#a13616856 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Problem with wicket authentication

Looks good to me. I'm using just like you are. Are you sure that your wicket application class is correct (i.e., that your filter is actually using WicketApplication, and not WebApplication or something like that)? I sugguest putting some breakpoints and checking the logs. Your getHomePageCl

Re: Problem with wicket authentication

> } >> > >> > >> > And finally, the admin page to protect: >> > >> > @AuthorizeInstantiation("USER") >> > public class AdminPage extends WebPage { >> > } >> > >> > The problem is that a click from the HomePage always brings the >> AdminPage, without any >> > LoginPage displayed. >> > >> > I used Wicket 1.3 beta4. >> > >> > After reading the Wicket example and 2 tutorials on authentication, I >> really can't see what I'm missing. >> > Any idea ? >> > >> > Hugues >> > >> > >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - Michael Sparer http://talk-on-tech.blogspot.com -- View this message in context: http://www.nabble.com/Problem-with-wicket-authentication-tf4751663.html#a13602398 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Problem with wicket authentication

you have not used it correctly return a Roles object and not null @Override public Roles getRoles() { return new Roles("ADMIN"); } @AuthorizeInstantiation("ADMIN") public class AdminPage extends WebPage { } On 11/6/07, Maurice Marrink <[EMAIL PROTECTED]> wrote: > > You are using the wr

Re: Problem with wicket authentication

You are using the wrong authorization framework! :) No seriously now. I don't know what is wrong with your code, although the authenticate method might give some useful debugging info. There is however a second authorization framework for wicket called Swarm. you might want to check it out. http:/

Problem with wicket authentication

Hi, I would like to use Wicket authentication, as in the examples. So I modified the Wicket QuickStart project to use authentication, like this: public class WicketApplication extends AuthenticatedWebApplication { public WicketApplication() { } public Class getHomePage() { return