the "wicket approach" is 2 or 3 classes that implement the infrastructure. the use well defined public interfaces to implement it. if it doesnt work for you, then simply roll your own implementation.
-igor On Tue, Mar 29, 2011 at 9:37 AM, hrbaer <[email protected]> wrote: > Hi all, > > my web application is using the wicket authentication approach > (AuthenticatedWebSession) and all my "secure" java files are marked with > "@AuthorizeInstantiation("ADMIN")" > So once I added this annotation there is no chance to bypass the > authentication. > > But what if there is the need to be flixible? What if for some users the > page A should be secure and for others don't? > > Let's assume there is is page with e.g. contact informations and a user can > decide for his own if the page should be accessible with or without > authentication. How can I achieve that without using the wicket approach? At > the moment it don't think that the wicket approach is the right one?! > > Thanks in advance. > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/flexible-authentication-tp3415413p3415413.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
