Hi,

Our base wicket app is deploy around 40-50 times on a couple of tomcats.
Each instance has a different configuration but the code base is the same
app.
Each instance has its own context and it looks something like this:
app a : baseurl/a
app baba: baseurl/baba

Currently the authentication and authorization for each site is handled by
the wicket app assigned to that context.
We implemented IAuhorizationStrategy and are using the signin page from the
examples + captcha after a couple of tries.

We want an app at baseurl/login that will take care of loging in instead of
all the different apps doing it for themselves.
Whats the best way to implement such a CAS mechanism? (preferably using
wicket, spring is ok too)

Thanks,
Sam.

Reply via email to