Example usage for org.springframework.security.config.annotation.web.configuration WebSecurityConfigurerAdapter subclass-usage

List of usage examples for org.springframework.security.config.annotation.web.configuration WebSecurityConfigurerAdapter subclass-usage

  1. HOME
  2. Java
  3. org.springframework.security.config.annotation.web.configuration.*
  4. WebSecurityConfigurerAdapter
  5. Example usage for org.springframework.security.config.annotation.web.configuration WebSecurityConfigurerAdapter subclass-usage

Introduction

In this page you can find the example usage for org.springframework.security.config.annotation.web.configuration WebSecurityConfigurerAdapter subclass-usage.

Usage

From source file docs.security.RememberMeSecurityConfiguration.java

/**
 * @author rwinch
 */
@EnableWebSecurity
@EnableSpringHttpSession
public class RememberMeSecurityConfiguration extends WebSecurityConfigurerAdapter {

From source file org.test.skeleton.core.config.WebSecurityConfig.java

@Configuration
@EnableWebMvcSecurity
public class WebSecurityConfig extends WebSecurityConfigurerAdapter {

    @Override
    protected void configure(HttpSecurity http) throws Exception {

From source file project.security.WebSecurityConfiguration.java

@Configuration
@EnableWebSecurity
@EnableWebMvcSecurity
public class WebSecurityConfiguration extends WebSecurityConfigurerAdapter {

    @Autowired

From source file hu.fnf.devel.wishbox.gateway.SecurityConfiguration.java

/**
 * Created by Balint Csikos (csikos.balint@fnf.hu) on 22/03/15.
 */

@Configuration
@EnableGlobalMethodSecurity(securedEnabled = true)

From source file shiver.me.timbers.spring.security.integration.JwtCustomPrincipleSecurityConfigurationAnnotation.java

@Configuration
@EnableAutoConfiguration
@EnableWebSecurity
@EnableJwtAuthentication
@Import({ JwtCustomPrincipleConfiguration.class, SpringSecurityControllerConfiguration.class })
public class JwtCustomPrincipleSecurityConfigurationAnnotation extends WebSecurityConfigurerAdapter {

From source file runtheshow.frontend.config.SecurityConfiguration.java

/**
 *
 * @author maxim
 */
@EnableAutoConfiguration
@EnableWebSecurity

From source file uk.ac.soton.itinnovation.sad.service.configuration.SecurityConfig.java

/**
 * Ensures ReportsController is not affected by user authentication.
 */
@Configuration
@EnableWebSecurity
public class SecurityConfig extends WebSecurityConfigurerAdapter {

From source file com.devnexus.ting.web.config.WebSecurityConfig.java

/**
 * @author Gunnar Hillert
 *
 */
@SuppressWarnings("deprecation")
@EnableWebSecurity

From source file net.prasenjit.security.login.SecurityConfiguration.java

@Configuration
@Order(SecurityProperties.ACCESS_OVERRIDE_ORDER)
public class SecurityConfiguration extends WebSecurityConfigurerAdapter {

    @Autowired
    private AuthenticationManager authenticationManager;

From source file com.mec.Security.WebSecurityConfig.java

/**
 Here we have decided that everyone can access the / route, and that the /login route is only publicly available for POST requests. For all other routes, authentication is required. You may have noted that the JWTLoginFilter class and the JWTAuthenticationFilter class are missing. We will create them soon, but their goal is to filter for the /login route, and every other route, to decide what should happen when someone access these routes. In this class, we also added a default account that we can use to test our application.
    
The great thing here is that we have now secured our application without having to change code for existing routes. We did not alter our previously created UserController, nor did we have to write any xml-configuration.
    
The classes JWTLoginFilter and JWTAuthenticationFilter will handle logging in and authenticating users, respectively. Before we can use these classes, however, we need to create a class that can handle JWTs.