Hi!
We have the same situation in one of our web applications (profile pages
may be hidden for everyone except the profile owner). Since I wasn't
able to find a clean way to check such conditions from our page
authorization strategy, I added that to the checks I already had in the
page constr
with this because I'm not sure why you have the requirement of being
secure for some users but not secure for others.
From: hrbaer
To: users@wicket.apache.org
Date: 03/29/2011 12:37 PM
Subject:flexible authentication
Hi all,
my web application is using the wicket authen
Thanks for all the good hints ... let me check the links/advices.
Hopefully there is no need to ask any further questions :)
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/flexible-authentication-tp3415413p3416489.html
Sent from the Users forum mailing list archive
ou have the requirement of being
secure for some users but not secure for others.
From: hrbaer
To: users@wicket.apache.org
Date: 03/29/2011 12:37 PM
Subject:flexible authentication
Hi all,
my web application is using the wicket authentication approach
(AuthenticatedWebSessio
there is no option to make it more flexible.
>
> What I'm interested in is if there is any chance to use "out of the box"
> functionality of wicket to solve this issue.
>
> Thanks in advance.
>
> --
> View this message in context:
> http://apache-wicket.184294
to make it more flexible.
What I'm interested in is if there is any chance to use "out of the box"
functionality of wicket to solve this issue.
Thanks in advance.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/flexible-authentication-tp3415413p341545
t; 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.na
e 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 U