Grails Spring Security使用https重定向到登录页面

我还使用https和负载均衡器在AWS上使用Spring Security Core 2.0-RC4托管我的Grails应用程序,感谢spock99(上图)和AWS的Ravi L,我得到了它的工作.

我在config.groovy中做了以下事情:

    // Required because user auth uses absolute redirects
    grails.serverURL = "http://example.com"

    grails.plugin.springsecurity.secureChannel.definition = [
        '/assets/**':     'ANY_CHANNEL',// make js, css, images available to logged out pages
        '/**':            'REQUIRES_SECURE_CHANNEL',
    ]

    // overriding values in DefaultSecurityConfig.groovy from the SpringSecurityCore 2.0-RC4 
    grails.plugin.springsecurity.secureChannel.useHeaderCheckChannelSecurity = true
    grails.plugin.springsecurity.portMapper.httpPort = 80
    grails.plugin.springsecurity.portMapper.httpsPort = 443

注意:Spring Security Core 2.0-RC4中不需要以下内容 - 它们已经在DefaultSecurityConfig.groovy中

    secureHeaderName = 'X-Forwarded-Proto'
    secureHeaderValue = 'http'
    insecureHeaderName = 'X-Forwarded-Proto'
    insecureHeaderValue = 'https'

我得到了错误的'不健康'读数,因为点击'/'会返回302重定向到/ login/auth,所以我将一个health()方法添加到HomeController(我映射到'/ health')以供AWS点击:

    class HomeController {
        @Secured('IS_AUTHENTICATED_FULLY')
        def index() { }

        @Secured('permitAll')
        def health() { render '' }
    }

关键是我在Load Balancer上运行多个实例时没有正确处理会话cookie(在将最小实例设置为2之前我没有发现这一点),所以为了让用户能够登录并保持登录状态,我在AWS上做了以下事情:

1.  At Services / Elastic Beanstalk / Configuration / Load Balancing 
    a. set Application health check URL: /health
    b. left Session Stickiness: unchecked
2. At Services / EC2 / Load Balancers / Description / Port Configuration:
    For both port 80 (HTTP)  and 443 (HTTPS)
        1. Edit and select 'Enable Application Generated Cookie Stickiness'
        2. Cookie Name: JSESSIONID