First, the SS default filter
When the configured HTTP is auto-configured, the default is to pass the SS 11 filters:
1,httpsessioncontextintegrationfilter: Put the SecurityContext in the session into the Securitycontextholder, empty after use;
2,logoutfilter: Processing the logout request, the default request address is:/j_spring_security_logout;
3,authenticationprocessingfilter: Authentication filter, processing from login, default only processing:/j_spring_security_check;
4,? ? Defaultloginpagegeneratingfilter ? ? : Spring comes with the login interface, no skin, generally used for testing, the default address is:/j_spring_security_login, support user name password and rememberme;
5,basicprocessingfilter: Basic certification. functions similar to 3;
6,securitycontextholderawarerequestfiler: Packaging customer requests, provide some additional data for the follow-up procedure;
7,remembermeprocessingfilter: Realize ' remember me ' function;
8,anonymousprocessingfilter: Anonymous login filter, for users who do not log in to assign anonymous permissions (anonymous also requires permission, otherwise you can only see the login page);
9,exceptiontranslationfilter: Handle filtersecurityinterceptor run out of abnormal;
sessionfixationprotectionfilter: Defense session forgery attack filter;
One,filtersecurityinterceptor: User Rights filter, filter out three kinds of situations:
A, the user is not logged in:authenticationcredentialsnotfoundexception "has not been certified abnormal";
b, Login without permission: accessdeniedexception "Access exception denied";
C, Login cut have permission, release.
Filters in spring security