Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I just went through the same scenario. Got stuck on the https, then the redirects, and now all is well. Use these Config.groovy settings:</p> <pre><code>grails.plugin.springsecurity.secureChannel.useHeaderCheckChannelSecurity = true grails.plugin.springsecurity.portMapper.httpPort = 80 grails.plugin.springsecurity.portMapper.httpsPort = 443 grails.plugin.springsecurity.secureChannel.secureHeaderName = 'X-Forwarded-Proto' grails.plugin.springsecurity.secureChannel.secureHeaderValue = 'http' grails.plugin.springsecurity.secureChannel.insecureHeaderName = 'X-Forwarded-Proto' grails.plugin.springsecurity.secureChannel.insecureHeaderValue = 'https' </code></pre> <p>Note for those not using springsecurity 2.0, it is 'plugins' and not 'plugin' without the 's'.</p> <p>My beanstalk load balancer settings look like this (I have an SSL cert installed, I didn't show it):</p> <p><img src="https://i.stack.imgur.com/kAH8v.png" alt="enter image description here"></p> <p>In the EC2 load balancer settings make sure your listeners are set right:</p> <p><img src="https://i.stack.imgur.com/aHvQU.png" alt="enter image description here"></p> <p>And finally in the EC2 security groups make sure the EB accepts requests on ports 80 and 443 from the ELB:</p> <p><img src="https://i.stack.imgur.com/xp638.png" alt="enter image description here"></p> <p>Note that nowhere in my setup of anything do I ever reference ports 8080 or 8443, even though that is what I use on my localhost for testing. Somebody reading this may think about trying to use those ports to fix the issues. My setup didn't require that.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload