Our client unfortunately wants to have urls be able to contain the user's 
login and a hashed/encrypted password so that the user can avoid having to 
waste time on the login page.   We can't really convince them that it may not 
be a good idea.   Essentially they want single-signon, but they're not 
prepared to work with the it department on that at this time (and I'm not 
sure how to do that in wicket yet, either).   So what they really, really 
want is that when our swing app brings up a web page in a browser, we add the 
user's login and hashed password to the url.

But I'm having trouble figuring out how or where to grab that info and bypass 
the login page redirect, and the login page can't seem to grab that info from 
the request.    Which makes sense since the page parameters are normally 
really for the original page and not the login page.

I've been looking at: AuthenticatedWebApplicationonUnauthorizedInstantiation, 
but it's final so I can't override it, and I'm not really sure if it's the 
right place anyway.   I've added my own 
IUnauthorizedComponentInstantiationListener, but I'm not sure how to get the 
request parameters in the listener.

Does anyone have any hints?

Thanks,
Tom

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to