为了与Tivoli Access Manager集成，我已经在我的Grails应用程序中实现了 Spring 安全性预激活过滤器。

筛选器针对Web应用程序中的每个请求被调用-尽管该筛选器返回与先前请求相同的主体，但它似乎会创建一个新 session 。我创建了一个ApplicationListener来侦听身份验证事件，并且可以看到一个新的AuthenticationSuccessEvent，其中每个请求都有一个新的 session ID。

这意味着我的所有 session 变量都会在每个请求中清除-没什么大不了的，但是它破坏了上载器插件。

当我打开预身份验证筛选器的调试日志记录时，我看到它认为主体已更改，即使它没有更改:

2015-03-04 11:34:57.769 foobar.TamAuthenticationFilter Checking secure context token: org.springframework.security.web.authentication.preauth.PreAuthenticatedAuthenticationToken@f0666480: Principal: grails.plugin.springsecurity.userdetails.GrailsUser@3125618: Username: 66734; Password: [PROTECTED]; Enabled: true; AccountNonExpired: true; credentialsNonExpired: true; AccountNonLocked: true; Granted Authorities: ROLE_ADMIN,ROLE_APPROVER; Credentials: [PROTECTED]; Authenticated: true; Details: org.springframework.security.web.authentication.WebAuthenticationDetails@fffde5d4: RemoteIpAddress: 0:0:0:0:0:0:0:1; SessionId: 87928D9E25D98DD3CCFAC5D67689E609; Granted Authorities: ROLE_ADMIN, ROLE_APPROVER
2015-03-04 11:34:57.770 foobar.TamAuthenticationFilter Pre-authenticated principal has changed to 66734 and will be reauthenticated
2015-03-04 11:34:57.770 foobar.TamAuthenticationFilter Invalidating existing session
2015-03-04 11:34:57.771 foobar.TamAuthenticationFilter preAuthenticatedPrincipal = 66734, trying to authenticate

package foobar

import org.springframework.security.web.authentication.preauth.AbstractPreAuthenticatedProcessingFilter
import grails.util.Environment
import grails.util.Holders
import groovy.util.logging.Log4j

@Log4j
class TamAuthenticationFilter extends   AbstractPreAuthenticatedProcessingFilter {

java.lang.Object getPreAuthenticatedCredentials(javax.servlet.http.HttpServletRequest request)
{
    "N/A"
}

java.lang.Object getPreAuthenticatedPrincipal(javax.servlet.http.HttpServletRequest request)
{
    Long staffId = getStaffIdFromTamHeader(request)
    if(!staffId)
        log.error "iv-user header not found"

    return staffId
}

/**
 * Get Staff ID from the ivUser Tamheader.
 * @param request
 * @return
 */
static public Long getStaffIdFromTamHeader(request) {
    return request.getHeader("iv-user")
}

}

 package foobar

 import groovy.util.logging.Log4j
 import org.springframework.context.ApplicationListener
 import org.springframework.security.authentication.event.AbstractAuthenticationEvent


 @Log4j
 class LoggingSecurityEventListener implements
    ApplicationListener<AbstractAuthenticationEvent> {

void onApplicationEvent(AbstractAuthenticationEvent event) {

    def username = event.authentication.principal
    def address = event.authentication.details.remoteAddress
    def sessionId = event.authentication.details.sessionId

    log.info "event=${event.class.simpleName} username=${username} remoteAddress=${address} sessionId=${sessionId}"

}

 }

beans = {
//
// grabs the user id from the tam headers 
//
tamAuthenticationFilter(TamAuthenticationFilter) {
    authenticationManager = ref('authenticationManager')
    checkForPrincipalChanges = true
}

tamAuthenticationProvider(PreAuthenticatedAuthenticationProvider) {
   preAuthenticatedUserDetailsService = ref('authenticationUserDetailsService')
}

//
// we do not want to redirect to the auth/login page since we are using tam
//
authenticationEntryPoint(Http403ForbiddenEntryPoint)

securityEventListener(LoggingSecurityEventListener)
}

 grails.plugin.springsecurity.useSecurityEventListener = true
 grails.plugin.springsecurity.providerNames = ['tamAuthenticationProvider']

 grails.plugin.springsecurity.userLookup.userDomainClassName = 'strobe.auth.User'
 grails.plugin.springsecurity.userLookup.authorityJoinClassName = 'strobe.auth.UserRole'
 grails.plugin.springsecurity.authority.className = 'strobe.auth.Role'
 grails.plugin.springsecurity.securityConfigType="InterceptUrlMap"
 grails.plugin.springsecurity.interceptUrlMap = [
                                            '/foobar/**':                   ['ROLE_USER']]

 def init = { servletContext ->                   SpringSecurityUtils.clientRegisterFilter('tamAuthenticationFilter',
            SecurityFilterPosition.PRE_AUTH_FILTER.order + 10)
 }

最佳答案

我已经找到了解决问题的方法-我从getPreauthenticatedPrincipal()返回了Long，这混淆了 Spring 的安全性，因为AbstractPreauthenticatedProcessingFilter中的requireAuthentication()方法具有以下代码行:

    if ((principal instanceof String) && currentUser.getName().equals(principal)) {
        return false;
    }

java.lang.Object getPreAuthenticatedPrincipal(javax.servlet.http.HttpServletRequest request)

关于session - Spring Security预身份验证-给我一个新的 session ，即使主体未更改，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/28843401/