2013-02-12 16 views
6

ho bisogno la mia sicurezza di avere la seguente logica:personalizzato Primavera Filtri 3.0 Sicurezza, entrypoints multipli, AuthenticationProvider

  1. Verificare la presenza di un parametro di intestazione
  2. A seconda della presenza della paremeter fare sia un redirect a una pagina di accesso (se non autenticata) o controllare il token di autenticazione di base

In entrambi i casi, ho lo stesso provider di autenticazione, ma non posso farlo funzionare. L'entrypoint delegare funziona bene, ma non ho mai entrare nella mia authenticationprovider personalizzato ...

Ecco la mia configurazione di sicurezza:

<security:global-method-security 
    secured-annotations="enabled" /> 

<security:http entry-point-ref="delegatingAuthenticationEntryPoint" 
    use-expressions="true" auto-config="false"> 
    <!-- <security:custom-filter position="FORM_LOGIN_FILTER" --> 
    <!-- ref="usernamePasswordAuthenticationFilter" /> --> 
    <!-- <security:custom-filter position="BASIC_AUTH_FILTER" --> 
    <!-- ref="basicAuthenticationFilter" /> --> 
    <security:intercept-url pattern="/login*" 
     filters="none" /> 
    <security:intercept-url pattern="/portimaLogin*" 
     filters="none" /> 
    <security:intercept-url pattern="/**" 
     access="isAuthenticated()" /> 
</security:http> 

<bean id="delegatingAuthenticationEntryPoint" 
    class="org.springframework.security.web.authentication.DelegatingAuthenticationEntryPoint"> 
    <constructor-arg> 
     <map> 
      <entry key="hasHeader('portima','true')" value-ref="PortimaLoginUrlAuthenticationEntryPoint" /> 
     </map> 
    </constructor-arg> 
    <property name="defaultEntryPoint" ref="authenticationEntryPoint" /> 
</bean> 

<bean id="usernamePasswordAuthenticationFilter" 
    class="org.springframework.security.web.authentication.UsernamePasswordAuthenticationFilter"> 
    <property name="authenticationManager" ref="authenticationManager" /> 
    <property name="authenticationFailureHandler" ref="authenticationFailureHandler" /> 
</bean> 

<bean id="basicAuthenticationFilter" 
    class="org.springframework.security.web.authentication.www.BasicAuthenticationFilter"> 
    <property name="authenticationManager" ref="authenticationManager" /> 
    <property name="authenticationEntryPoint" ref="authenticationEntryPoint" /> 
</bean> 

<bean id="PortimaLoginUrlAuthenticationEntryPoint" 
    class="be.ap.common.security.spring.PortimaLoginUrlAuthenticationEntryPoint"> 
    <property name="loginFormUrl" value="${portima.login.page}" /> 
</bean> 

<bean id="authenticationEntryPoint" 
    class="org.springframework.security.web.authentication.www.BasicAuthenticationEntryPoint"> 
    <property name="realmName" value="AP" /> 
</bean> 

<security:authentication-manager alias="authenticationManager"> 
    <security:authentication-provider 
     ref="authenticationProvider" /> 
</security:authentication-manager> 

<bean id="authenticationProvider" class="be.ap.common.security.spring.APAuthenticationProvider" /> 

<bean id="userDetailsService" class="be.ap.common.security.spring.APUserDetailsService" /> 

Qualche idea?

+0

Il tuo AuthenticationProvider personalizzato implementa correttamente il metodo 'supports()'? Se restituisce false per la classe 'UsernamePasswordAuthenticationToken', non verrà mai richiesto di elaborare i token di autenticazione creati dai filtri. – zagyi

+0

Non funziona nemmeno nel metodo di supporto ... –

+0

@Override supporti booleani pubblici (classe autenticazione) { return UsernamePasswordAuthenticationToken.class.isAssignableFrom (autenticazione); } –

risposta

12

Finalmente l'ho fatto funzionare.

Ecco il mio file di contesto:

<security:http entry-point-ref="delegatingAuthenticationEntryPoint" 
    use-expressions="true"> 
    <security:custom-filter position="PRE_AUTH_FILTER" 
     ref="preAuthenticationFilter" /> 
    <security:custom-filter position="FORM_LOGIN_FILTER" 
     ref="usernamePasswordAuthenticationFilter" /> 
    <security:custom-filter position="BASIC_AUTH_FILTER" 
     ref="basicAuthenticationFilter" /> 
    <security:intercept-url pattern="/login*" 
     filters="none" /> 
    <security:intercept-url pattern="/portimaLogin*" 
     filters="none" /> 
    <security:intercept-url pattern="/accessDenied*" 
     filters="none" /> 
    <security:intercept-url pattern="/**" 
     access="isAuthenticated()" /> 
    <security:access-denied-handler ref="accessDeniedHandler" /> 
</security:http> 

<!-- Spring Security Custom Filters --> 

<bean id="usernamePasswordAuthenticationFilter" 
    class="org.springframework.security.web.authentication.UsernamePasswordAuthenticationFilter"> 
    <property name="authenticationManager" ref="authenticationManager" /> 
    <property name="authenticationFailureHandler" ref="authenticationFailureHandler" /> 
</bean> 

<bean id="basicAuthenticationFilter" 
    class="org.springframework.security.web.authentication.www.BasicAuthenticationFilter"> 
    <property name="authenticationManager" ref="authenticationManager" /> 
    <property name="authenticationEntryPoint" ref="authenticationEntryPoint" /> 
</bean> 

<bean id="preAuthenticationFilter" class="be.ap.common.security.spring.APPreAuthenticationFilter"> 
    <property name="authenticationManager" ref="authenticationManager" /> 
</bean> 

<!-- Spring Security Custom EntryPoint --> 

<bean id="delegatingAuthenticationEntryPoint" 
    class="org.springframework.security.web.authentication.DelegatingAuthenticationEntryPoint"> 
    <constructor-arg> 
     <map> 
      <entry key="hasHeader('portima','true')" value-ref="PortimaLoginUrlAuthenticationEntryPoint" /> 
     </map> 
    </constructor-arg> 
    <property name="defaultEntryPoint" ref="authenticationEntryPoint" /> 
</bean> 

<bean id="PortimaLoginUrlAuthenticationEntryPoint" 
    class="be.ap.common.security.spring.PortimaLoginUrlAuthenticationEntryPoint"> 
    <property name="loginFormUrl" value="${portima.login.page}" /> 
</bean> 

<bean id="authenticationEntryPoint" 
    class="be.ap.common.security.spring.APBasicAuthenticationEntryPoint"> 
    <property name="realmName" value="AP" /> 
</bean> 
<bean id="accessDeniedHandler" 
    class="org.springframework.security.web.access.AccessDeniedHandlerImpl"> 
    <property name="errorPage" value="/accessDenied" /> 
</bean> 

<bean id="authenticationFailureHandler" 
    class="org.springframework.security.web.authentication.ExceptionMappingAuthenticationFailureHandler"> 
    <property name="exceptionMappings"> 
     <props> 
      <prop 
       key="org.springframework.security.authentication.BadCredentialsException"> 
       /accessDenied 
      </prop> 
      <prop 
       key="org.springframework.security.authentication.CredentialsExpiredException"> 
       /accessDenied 
      </prop> 
      <prop key="org.springframework.security.authentication.LockedException"> 
       /accessDenied 
      </prop> 
      <prop 
       key="org.springframework.security.authentication.DisabledException"> 
       /accessDenied 
      </prop> 
     </props> 
    </property> 
</bean> 

<!-- Spring Security Authentication Manager --> 

<security:authentication-manager alias="authenticationManager"> 
    <security:authentication-provider 
     ref="authenticationProvider" /> 
</security:authentication-manager> 

<bean id="authenticationProvider" class="be.ap.common.security.spring.APAuthenticationProvider" /> 

<bean id="userDetailsService" class="be.ap.common.security.spring.APUserDetailsService" /> 

<!-- for Mock --> 
<bean id="SSOService" class="be.ap.security.service.SSOServiceMockImpl" /> 

Come potete vedere ho aggiunto un paio di cose troppo.

Per risolvere il problema, ho rimosso l'attributo auto-config, decommentato i filtri e li ho definiti correttamente.

Per gli altri che vogliono una rapida comprensione di ciò che fa, qui è il flusso:

  1. PRE_AUTH_FILTER controllerà uno SSO come servizio per precompilare l'oggetto di autenticazione (se già autenticato in SSO)
  2. delegatingAuthenticationEntryPoint poi decidere come autenticare seconda richiesta di intestazione
  3. I due modi sono:
    • LoginUrlAuthenticationEntryPoint personalizzato
    • personalizzato BasicAuthenticationEntryPoint

BasicAuth e LoginURLAuth utilizzano lo stesso AuthenticationProvider quando PreAuth usa il mio servizio SSO.

Spero che aiuti qualcun altro!

Problemi correlati