I'm relatively new to Wicket and trying not to carry forward any
preconceived notions from other frameworks. What is the
suggested/preferred means of authenticating single sign-on requests
from another application? In particular, I'm thinking about MAC
Hi Igor,
Apologies that I wasn't more detailed. More specifically:
1. User is in application X
2. User clicks on link to goto application Y
3. Application X constructs a URL with relevant parameters (ex.
username) and an md5 hash with the shared secret
4. Application X redirects to this URL.
5.
Not much in the way of clues... The ResultPage is being instantiated,
but instead of being rendered the HomePage is reloaded. Everything is
fine on GlassFish v2.. but Sun Java App Server 7 = no dice. I'm at a
loss for what to do next.
On Mon, Aug 10, 2009 at 10:29 AM, Igor
That's the thing that I can't seem to figure out. The app works on
GlassFish v2 and Tomcat, but I'm having this problem on Sun Java App
Server 7.
As suggested in ##wicket, I switched from the wicket filter to the
wicket servlet - but I'm still having the problem where there are two
?wicket in
It doesn't seem to be a session problem. If I take off the first
?wicket: in the URL, it will correctly load the ResultPage - so the
session is still valid. I'm continuing to scratch my head as to why
there are two ?wicket params in the URL... Very frustrating.
On Mon, Aug 10, 2009 at 4:32 PM,
In my quest to solve this problem, I'm mounting all my pages using
HybridUrlCodingStrategy to see if that will negate the extra ?wicket
param in the URL. Worked fine on GlassFish, but as soon as I moved it
over to Sun App Server 7 I got:
Exception in rendering component: [MarkupContainer
