<div id="readability-page-1" class="page"><div id="dkContent" role="main">

					

					<p>
						<h2><span>네로개발일기</span></h2>
					</p>

					                
                    
						


						
							
							<div>
								<p><strong><a href="/category/web/Spring">web/Spring</a></strong></p><h3>[Spring Security] SecurityConfig 리팩토링 - WebSecurityConfigurerAdapter 상속 제거, Resource Filter Chain 설정</h3>
								<p><span>ner.o
                                <span></span>2023. 1. 16. 12:27
								
							</span>
							</p></div>

							<div><figure data-ke-mobilestyle="widthOrigin" data-origin-width="768" data-origin-height="402"><span data-url="https://blog.kakaocdn.net/dn/seiUl/btrWbUv5UiH/OyxrFVufrOXkhOezjQC6K0/img.png" data-lightbox="lightbox"><img src="https://blog.kakaocdn.net/dn/seiUl/btrWbUv5UiH/OyxrFVufrOXkhOezjQC6K0/img.png" onerror="this.onerror=null; this.src='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png'; this.srcset='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png';" data-origin-width="768" data-origin-height="402"></span></figure>

<h3 data-ke-size="size23"><b>1. Spring Security Config 리팩토링</b></h3>
<p data-ke-size="size16">Spring Security 버전업이 되면서 기존 프로젝트의 문제점이 생기기 시작했다. 해당 문제점에 대해 알아보고 리팩토링을 하자.</p>

<ul data-ke-list-type="disc">
<li>WebSecurityConfigurerAdapter 상속 제거</li>
<li>Resource Filter Chain 설정</li>
</ul>
<h3 data-ke-size="size23"><b>2. 개발 환경</b></h3>
<ul data-ke-list-type="disc">
<li>Spring Boot 2.7.6</li>
<li>Spring Security 5.7.6</li>
<li>Java 11</li>
<li>Gradle 7.5.1</li>
</ul>
<h3 data-ke-size="size23"><b>3. 기존 SecurityConfig</b></h3>
<p data-ke-size="size16">일반적으로 많이 사용하는 SecurityConfig이다.</p>
<pre id="code_1673586858850" data-ke-language="java" data-ke-type="codeblock"><code>@Configuration
@EnableWebSecurity // Spring Security 활성화
public class SecurityConfig extends WebSecurityConfigurerAdapter {
    
    @Override
    public void configure(WebSecurity web) {
        // resource 에 대해 Spring Security FilterChain 제외
        web.ignoring().antMatchers("/resources/**");
    }
    
    @Override
    protected void configure(HttpSecurity http) throws Exception {
        http.authorizeRequests()
                .mvcMatchers("/", "/login", "/sign-up", "/check-email-token"
                        , "/email-login", "/check-email-login", "/login-link", "/login-by-email").permitAll()
                .mvcMatchers(HttpMethod.GET, "/profile/*").permitAll()
                .anyRequest().authenticated().and()
            .formLogin()
                .loginPage("/login").permitAll()
            .logout()
                .logoutSuccessUrl("/");
    }
}</code></pre>
<h4 data-ke-size="size20"><b>ant pattern을 이용한 ignore 처리가 권장되지 않는다.</b></h4>
<p data-ke-size="size16">해당 설정으로 실행시 하단과 같은 WARN 로그가 발생한다.</p>
<pre id="code_1673586936561" data-ke-language="bash" data-ke-type="codeblock"><code>You are asking Spring Security to ignore Ant [pattern='/resource/**']. This is not recommended -- please use permitAll via HttpSecurity#authorizeHttpRequests instead.</code></pre>
<p data-ke-size="size16">이 로그는 Spring Security 5.5.x에 추가되었으며 <a href="https://github.com/spring-projects/spring-security/issues/10938" target="_blank" rel="noopener">Spring Security Github Issue</a>에서 확인할 수 있다. 간략히 요약해보자면,</p>
<blockquote data-ke-style="style2">web.ignoring()은 Spring Security 가 해당 엔드포인트에 보안헤더 또는 기타 보호 조치를 제공할 수 없다. 대신에 permitAll() 메서드를 사용하여 권한 검증 없이 요청을 보호할 수 있다. 이러한 이유때문에 해당 경고메시지를 알려주었다.</blockquote>
<p data-ke-size="size16">또한, static resource에 대해 SecurityFilterChain을 추가하는 방법에 대해서 알려주었는데 해당 방안은 밑에서 알아보겠습니다.</p>

<h4 data-ke-size="size20"><b>Spring Security 5.7.x 부터 WebSecurityConfigurerAdapter Deprecate 문제</b></h4>
<p data-ke-size="size16">Spring Security 5.7.x 부터 WebSecurityConfigurerAdapter가 Deprecated 되었다.</p>
<p data-ke-size="size16"><a href="https://spring.io/blog/2022/02/21/spring-security-without-the-websecurityconfigureradapter" target="_blank" rel="noopener">https://spring.io/blog/2022/02/21/spring-security-without-the-websecurityconfigureradapter</a></p>

<h3 data-ke-size="size23"><b>4. SecurityConfig 리팩토링</b></h3>
<h4 data-ke-size="size20"><b>WebSecurityConfigurerAdapter를 상속하기않고 적용</b></h4>
<p data-ke-size="size16">WebSecurityConfigurerAdapter를 상속하지 않고 필터체인을 구성하는 방법으론 SecurityFilterChain을 Bean으로 선언하는 방법이 있다. 이때 HttpSecurity를 주입받아 사용하면 된다.</p>
<pre id="code_1673593016953" data-ke-language="java" data-ke-type="codeblock"><code>@Configuration
@EnableWebSecurity
public class SecurityConfig {

    @Bean   
    public WebSecurityCustomizer webSecurityCustomizer() {
        return web -&gt; web.ignoring().antMatchers("/resources/**");   
    }

    @Bean
    public SecurityFilterChain filterChain(HttpSecurity http) throws Exception {
        http.authorizeRequests()
                .mvcMatchers("/", "/login", "/sign-up", "/check-email-token"
                        , "/email-login", "/check-email-login", "/login-link", "/login-by-email").permitAll()
                .mvcMatchers(HttpMethod.GET, "/profile/*").permitAll()
                .anyRequest().authenticated();

        http.formLogin()
                .loginPage("/login")
                .permitAll();

        http.logout()
                .logoutSuccessUrl("/");

        return http.build();
    }
}</code></pre>
<p data-ke-size="size16">WebSecurityConfigurerAdapter 상속을 제거하고 WebSecurityCustomizer 선언과 HttpSecurity의 build() 호출 후, 리턴하여 Bean으로 등록한다.</p>
<p data-ke-size="size16">HttpSecurityConfiguration을 확인해보면 HttpSecurity에 기본적인 설정을 한 후, prototype으로 Bean을 등록한다. 따라서 매번 주입받을 때 마다 새로운 인스턴스를 주입받을 수 있다.</p>

<p data-ke-size="size16"><b>➤ 주의사항</b></p>
<p data-ke-size="size16">WebSecurityConfigurerAdapter 상속과 SecurityFilterChain Bean 등록을 동시에 사용할 경우 아래와 같은 로그가 발생한다.</p>
<pre id="code_1673593450859" data-ke-language="bash" data-ke-type="codeblock"><code>Caused by: java.lang.IllegalStateException: Found WebSecurityConfigurerAdapter as well as SecurityFilterChain. Please select just one.</code></pre>

<h4 data-ke-size="size20"><b>Resource 용 SecurityFilterChain 적용</b></h4>
<p data-ke-size="size16">WebSecurityCustomizer 설정을 제거하고 @Order(0) 을 추가하여 먼저 FilterChain 을 타도록 지정한다. resources(css, js 등) 의 경우 securityContext 등에 대한 조회가 불필요 하므로 disable 합니다.</p>
<pre id="code_1673594159783" data-ke-language="java" data-ke-type="codeblock"><code>@Configuration
@EnableWebSecurity
public class SecurityConfig {

    @Bean
    public SecurityFilterChain filterChain(HttpSecurity http) throws Exception {
        http.authorizeRequests()
                .mvcMatchers("/", "/login", "/sign-up", "/check-email-token"
                        , "/email-login", "/check-email-login", "/login-link", "/login-by-email").permitAll()
                .mvcMatchers(HttpMethod.GET, "/profile/*").permitAll()
                .anyRequest().authenticated();

        http.formLogin()
                .loginPage("/login")
                .permitAll();

        http.logout()
                .logoutSuccessUrl("/");

        return http.build();
    }

    @Bean
    @Order(0)
    public SecurityFilterChain resources(HttpSecurity http) throws Exception {
        return http.requestMatchers(matchers -&gt; matchers.antMatchers( "/resources/**"))
                .authorizeHttpRequests(authorize -&gt; authorize.anyRequest().permitAll())
                .requestCache(RequestCacheConfigurer::disable)
                .securityContext(AbstractHttpConfigurer::disable)
                .sessionManagement(AbstractHttpConfigurer::disable).build();
    }
}</code></pre>



<p data-ke-size="size16"><span><b>&nbsp;출처&nbsp;</b></span></p>
<p data-ke-size="size16"><a href="https://spring.io/blog/2022/02/21/spring-security-without-the-websecurityconfigureradapter" target="_blank" rel="noopener">https://spring.io/blog/2022/02/21/spring-security-without-the-websecurityconfigureradapter</a></p>
<figure id="og_1673594284493" contenteditable="false" data-ke-type="opengraph" data-ke-align="alignCenter" data-og-type="article" data-og-title="Spring Security without the WebSecurityConfigurerAdapter" data-og-description="<p>In Spring Security 5.7.0-M2 we <a href=&quot;https://github.com/spring-projects/spring-security/issues/10822&quot;>deprecated</a> the <code>WebSecurityConfigurerAdapter</code>, as we encourage users to move towards a component-based security configuration.</p> <p" data-og-host="spring.io" data-og-source-url="https://spring.io/blog/2022/02/21/spring-security-without-the-websecurityconfigureradapter" data-og-url="https://spring.io/blog/2022/02/21/spring-security-without-the-websecurityconfigureradapter" data-og-image="https://scrap.kakaocdn.net/dn/t7ksy/hyRggjj1Bg/VOXspaDyNdSKgJaCqpGBp1/img.jpg?width=200&amp;height=200&amp;face=63_54_129_126"><a href="https://spring.io/blog/2022/02/21/spring-security-without-the-websecurityconfigureradapter" target="_blank" rel="noopener" data-source-url="https://spring.io/blog/2022/02/21/spring-security-without-the-websecurityconfigureradapter">

<div>
<p data-ke-size="size16">Spring Security without the WebSecurityConfigurerAdapter</p>
<p data-ke-size="size16">&lt;p&gt;In Spring Security 5.7.0-M2 we &lt;a href="https://github.com/spring-projects/spring-security/issues/10822"&gt;deprecated&lt;/a&gt; the &lt;code&gt;WebSecurityConfigurerAdapter&lt;/code&gt;, as we encourage users to move towards a component-based security configuration.&lt;/p&gt; &lt;p</p>
<p data-ke-size="size16">spring.io</p>
</div>
</a><img src="https://scrap.kakaocdn.net/dn/t7ksy/hyRggjj1Bg/VOXspaDyNdSKgJaCqpGBp1/img.jpg?width=200&amp;height=200&amp;face=63_54_129_126"></figure>
<p data-ke-size="size16"><a href="https://github.com/spring-projects/spring-security/issues/10938" target="_blank" rel="noopener">https://github.com/spring-projects/spring-security/issues/10938</a></p>
<figure id="og_1673594300339" contenteditable="false" data-ke-type="opengraph" data-ke-align="alignCenter" data-og-type="object" data-og-title="WARN when ignoring antMatchers - please use permitAll · Issue #10938 · spring-projects/spring-security" data-og-description="When I use web.ignoring().antMatchers() I'd like to see a DEBUG message instead of a WARNING for each ignored pattern. I'm confused by the message saying it's not recommended and I shou..." data-og-host="github.com" data-og-source-url="https://github.com/spring-projects/spring-security/issues/10938" data-og-url="https://github.com/spring-projects/spring-security/issues/10938" data-og-image="https://scrap.kakaocdn.net/dn/bFT6bb/hyRguaNRz1/2bSaKNHMgc8gtVKIjAYAdK/img.png?width=1200&amp;height=600&amp;face=0_0_1200_600"><a href="https://github.com/spring-projects/spring-security/issues/10938" target="_blank" rel="noopener" data-source-url="https://github.com/spring-projects/spring-security/issues/10938">

<div>
<p data-ke-size="size16">WARN when ignoring antMatchers - please use permitAll · Issue #10938 · spring-projects/spring-security</p>
<p data-ke-size="size16">When I use web.ignoring().antMatchers() I'd like to see a DEBUG message instead of a WARNING for each ignored pattern. I'm confused by the message saying it's not recommended and I shou...</p>
<p data-ke-size="size16">github.com</p>
</div>
</a><img src="https://scrap.kakaocdn.net/dn/bFT6bb/hyRguaNRz1/2bSaKNHMgc8gtVKIjAYAdK/img.png?width=1200&amp;height=600&amp;face=0_0_1200_600"></figure>
<p data-ke-size="size16"><a href="https://velog.io/@csh0034/Spring-Security-Config-Refactoring">https://velog.io/@csh0034/Spring-Security-Config-Refactoring</a></p>
<figure id="og_1673594308297" contenteditable="false" data-ke-type="opengraph" data-ke-align="alignCenter" data-og-type="article" data-og-title="[Spring Security] Config Refactoring" data-og-description="WebSecurityConfigurerAdapter Deprecated, Lambda DSL 적용, Resource Filter Chain 설정" data-og-host="velog.io" data-og-source-url="https://velog.io/@csh0034/Spring-Security-Config-Refactoring" data-og-url="https://velog.io/@csh0034/Spring-Security-Config-Refactoring" data-og-image="https://scrap.kakaocdn.net/dn/lPP3e/hyRgm4SMki/1rWJA2RKXDzae2S93CzAtk/img.png?width=1200&amp;height=600&amp;face=0_0_1200_600,https://scrap.kakaocdn.net/dn/EXCVH/hyRgsqvpX5/fLyUk2r6g99yC3AeIIfCRk/img.png?width=1200&amp;height=600&amp;face=0_0_1200_600,https://scrap.kakaocdn.net/dn/ccc7ZH/hyRgoaA38O/5NfN4BK7NtbZR6hZSYU5Ik/img.png?width=1200&amp;height=600&amp;face=0_0_1200_600"><a href="https://velog.io/@csh0034/Spring-Security-Config-Refactoring" target="_blank" rel="noopener" data-source-url="https://velog.io/@csh0034/Spring-Security-Config-Refactoring">

<div>
<p data-ke-size="size16">[Spring Security] Config Refactoring</p>
<p data-ke-size="size16">WebSecurityConfigurerAdapter Deprecated, Lambda DSL 적용, Resource Filter Chain 설정</p>
<p data-ke-size="size16">velog.io</p>
</div>
</a><img src="https://scrap.kakaocdn.net/dn/lPP3e/hyRgm4SMki/1rWJA2RKXDzae2S93CzAtk/img.png?width=1200&amp;height=600&amp;face=0_0_1200_600,https://scrap.kakaocdn.net/dn/EXCVH/hyRgsqvpX5/fLyUk2r6g99yC3AeIIfCRk/img.png?width=1200&amp;height=600&amp;face=0_0_1200_600,https://scrap.kakaocdn.net/dn/ccc7ZH/hyRgoaA38O/5NfN4BK7NtbZR6hZSYU5Ik/img.png?width=1200&amp;height=600&amp;face=0_0_1200_600"></figure>
</div>
							

							
								
							

							


						
					
                    
                

					

					

					

					

					

					
				</div></div>

개구린개구리

1. Spring Security Config 리팩토링
Spring Security 버전업이 되면서 기존 프로젝트의 문제점이 생기기 시작했다. 해당 문제점에 대해 알아보고 리팩토링을 하자.
 
WebSecurityConfigurerAdapter 상속 제거
Resource Filter Chain 설정
2. 개발 환경
Spring Boot 2.7.6
Spring Security 5.7.6
Java 11
Gradle 7.5.1
3. 기존 SecurityConfig
일반적으로 많이 사용하는 SecurityConfig이다.
@Configuration
@EnableWebSecurity // Spring Security 활성화
public class SecurityConfig extends WebSecurityConfigurerAdapter {
    
    @Override
    public void configure(WebSecurity web) {
        // resource 에 대해 Spring Security FilterChain 제외
        web.ignoring().antMatchers("/resources/**");
    }
    
    @Override
    protected void configure(HttpSecurity http) throws Exception {
        http.authorizeRequests()
                .mvcMatchers("/", "/login", "/sign-up", "/check-email-token"
                        , "/email-login", "/check-email-login", "/login-link", "/login-by-email").permitAll()
                .mvcMatchers(HttpMethod.GET, "/profile/*").permitAll()
                .anyRequest().authenticated().and()
            .formLogin()
                .loginPage("/login").permitAll()
            .logout()
                .logoutSuccessUrl("/");
    }
}
ant pattern을 이용한 ignore 처리가 권장되지 않는다.
해당 설정으로 실행시 하단과 같은 WARN 로그가 발생한다.
You are asking Spring Security to ignore Ant [pattern='/resource/**']. This is not recommended -- please use permitAll via HttpSecurity#authorizeHttpRequests instead.
이 로그는 Spring Security 5.5.x에 추가되었으며 Spring Security Github Issue에서 확인할 수 있다. 간략히 요약해보자면,
web.ignoring()은 Spring Security 가 해당 엔드포인트에 보안헤더 또는 기타 보호 조치를 제공할 수 없다. 대신에 permitAll() 메서드를 사용하여 권한 검증 없이 요청을 보호할 수 있다. 이러한 이유때문에 해당 경고메시지를 알려주었다.
또한, static resource에 대해 SecurityFilterChain을 추가하는 방법에 대해서 알려주었는데 해당 방안은 밑에서 알아보겠습니다.
 
Spring Security 5.7.x 부터 WebSecurityConfigurerAdapter Deprecate 문제
Spring Security 5.7.x 부터 WebSecurityConfigurerAdapter가 Deprecated 되었다.
https://spring.io/blog/2022/02/21/spring-security-without-the-websecurityconfigureradapter
 
4. SecurityConfig 리팩토링
WebSecurityConfigurerAdapter를 상속하기않고 적용
WebSecurityConfigurerAdapter를 상속하지 않고 필터체인을 구성하는 방법으론 SecurityFilterChain을 Bean으로 선언하는 방법이 있다. 이때 HttpSecurity를 주입받아 사용하면 된다.
@Configuration
@EnableWebSecurity
public class SecurityConfig {
    @Bean   
    public WebSecurityCustomizer webSecurityCustomizer() {
        return web -> web.ignoring().antMatchers("/resources/**");   
    }
    @Bean
    public SecurityFilterChain filterChain(HttpSecurity http) throws Exception {
        http.authorizeRequests()
                .mvcMatchers("/", "/login", "/sign-up", "/check-email-token"
                        , "/email-login", "/check-email-login", "/login-link", "/login-by-email").permitAll()
                .mvcMatchers(HttpMethod.GET, "/profile/*").permitAll()
                .anyRequest().authenticated();
        http.formLogin()
                .loginPage("/login")
                .permitAll();
        http.logout()
                .logoutSuccessUrl("/");
        return http.build();
    }
}
WebSecurityConfigurerAdapter 상속을 제거하고 WebSecurityCustomizer 선언과 HttpSecurity의 build() 호출 후, 리턴하여 Bean으로 등록한다.
HttpSecurityConfiguration을 확인해보면 HttpSecurity에 기본적인 설정을 한 후, prototype으로 Bean을 등록한다. 따라서 매번 주입받을 때 마다 새로운 인스턴스를 주입받을 수 있다.
 
➤ 주의사항
WebSecurityConfigurerAdapter 상속과 SecurityFilterChain Bean 등록을 동시에 사용할 경우 아래와 같은 로그가 발생한다.
Caused by: java.lang.IllegalStateException: Found WebSecurityConfigurerAdapter as well as SecurityFilterChain. Please select just one.
 
Resource 용 SecurityFilterChain 적용
WebSecurityCustomizer 설정을 제거하고 @Order(0) 을 추가하여 먼저 FilterChain 을 타도록 지정한다. resources(css, js 등) 의 경우 securityContext 등에 대한 조회가 불필요 하므로 disable 합니다.
@Configuration
@EnableWebSecurity
public class SecurityConfig {
    @Bean
    public SecurityFilterChain filterChain(HttpSecurity http) throws Exception {
        http.authorizeRequests()
                .mvcMatchers("/", "/login", "/sign-up", "/check-email-token"
                        , "/email-login", "/check-email-login", "/login-link", "/login-by-email").permitAll()
                .mvcMatchers(HttpMethod.GET, "/profile/*").permitAll()
                .anyRequest().authenticated();
        http.formLogin()
                .loginPage("/login")
                .permitAll();
        http.logout()
                .logoutSuccessUrl("/");
        return http.build();
    }
    @Bean
    @Order(0)
    public SecurityFilterChain resources(HttpSecurity http) throws Exception {
        return http.requestMatchers(matchers -> matchers.antMatchers( "/resources/**"))
                .authorizeHttpRequests(authorize -> authorize.anyRequest().permitAll())
                .requestCache(RequestCacheConfigurer::disable)
                .securityContext(AbstractHttpConfigurer::disable)
                .sessionManagement(AbstractHttpConfigurer::disable).build();
    }
}
 
 
 
 출처 
https://spring.io/blog/2022/02/21/spring-security-without-the-websecurityconfigureradapter
https://github.com/spring-projects/spring-security/issues/10938
https://velog.io/@csh0034/Spring-Security-Config-Refactoring

[Spring Security] SecurityConfig 리팩토링 - WebSecurityConfigurerAdapter 상속 제거, Resource Filter Chain 설정

댓글