Re: signOut and port

[brettTi]

Yea, I was already doing all that.  The issue was the :8443 in the url, which
is accurate but bothersome since we are trying to hide that with iptables.

Fixed it by throwing a RedirectToUrlException with the port number left out
of the url.



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/signOut-and-port-tp4254767p4284021.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: signOut and port

[Jeremy Thomerson]

On Mon, Jan 2, 2012 at 5:38 PM, brettTi  wrote:

> We're running a wicket app on jetty and having an issue with signout. The
> app
> runs on port 8443 and we have iptables redirecting from port 443.  This
> lets
> us go to https://ourap.lab without port numbers and without having the web
> app run as root.
>
> Everything is great until we do signout.  We have a LogoutPage that does
> this:
>
>   AuthenticatedWebSession.get().signOut();
>   setResponsePage(HomePage.class);
>
> Works fine, we get sent to the Login page.  Only problem is that the url
> has
> the :8443 port number in it.  For some reason, this is the end of the world
> for our users.
>
> Any ideas?  Thanks
>

Maybe a combination of these two things:

First, do the iptables packet redirection [1] - sounds like you have this
working.
Then, tell Wicket what port to send redirects to [2] - sounds like this may
fix your problem.

[1] http://wiki.eclipse.org/Jetty/Howto/Port80#Using_iptables
[2]
http://www.petrikainulainen.net/programming/tips-and-tricks/wicket-https-tutorial-part-one-creating-secure-webpages/


-- 
Jeremy Thomerson
http://wickettraining.com
*Need a CMS for Wicket?  Use Brix! http://brixcms.org*