Loading...
Important Notice - Forums is archived

To simplify things and help our users to be more productive, we have archived the current forum and focus our efforts on helping developers on Stack Overflow. You can post new questions on Stack Overflow or join our Discord channel.

Product icon
TUTORIAL

Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.

EC2 server port forwarding

Hugo Hanisch
6 years ago Jun 04, 2015 5:39pm
Matti Tahvonen
6 years ago Jun 04, 2015 9:10pm
Hugo Hanisch
6 years ago Jun 05, 2015 7:45pm
Hugo Hanisch
6 years ago Jun 15, 2015 8:39pm
Matti Tahvonen
6 years ago Jun 18, 2015 2:02pm
Hugo Hanisch
6 years ago Jun 18, 2015 6:33pm
David Wall
6 years ago Jun 18, 2015 8:04pm

I don't about your specific setup, but we set the 8080 connector to redirect to port 443 as that's the standard for HTTPS.  We then let iptables NAT redirect 80 to 8080 and 443 to 8443:

*nat
:PREROUTING ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A PREROUTING -p tcp -m tcp --dport 443 -j REDIRECT --to-ports 8443-A PREROUTING -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 8080

Be sure your app's web.xml includes a security constraint confidential if you'd like HTTP to auto-redirect to HTTPS, something like:

<security-constraint>
  <web-resource-collection>
    <web-resource-name>Entire Open eSignForms web app</web-resource-name>
    <url-pattern>/*</url-pattern>
  </web-resource-collection>
  <user-data-constraint>    <transport-guarantee>CONFIDENTIAL</transport-guarantee>  </user-data-constraint>
</security-constraint>

Also, not sure about your SSL, but the key alias defaults to "tomcat" but I presume that keyAlias works if that's how you set things up and you said https is working for you.

You can perhaps see more in our setup guide (see section on Tomcat and Linux):
https://github.com/OpenESignForms/openesignforms/wiki/InstallationUsingVaadin7
 

Hugo Hanisch
6 years ago Jun 30, 2015 4:37pm

Did that and worked!!!...thanks David!!!