Thursday, 11 February 2016

Integration Testing of Spring MVC:Applications: Security

By On

This blog is in continuation of my previous blog Applications: Security Configuration if you haven't read it please read it before this blogThe name of our security configuration file example ApplicationContext-security.xml and we can create the security configuration of our todo application by following these steps: 
  • Ensure that everyone can access static resources such as css files, images and Javascript files.     We can do this using the http element of the security namespace. All we have to do is to set the wanted url pattern (in our case /static/**) and the value of its security attribute to ‘none’.    success handler, authentication failure handler and logout success handler beans.
  • Ensure that everyone can access static resources such as css files, images and Javascript files.     We can do this using the http element of the security namespace. All we have to do is to set the wanted url pattern (in our case /static/**) and the value of its security attribute to ‘none’.    success handler, authentication failure handler and logout success handler beans.
  • Ensure that everyone can access static resources such as css files, images and Javascript files.     We can do this using the http element of the security namespace. All we have to do is to set the wanted url pattern (in our case /static/**) and the value of its security attribute to ‘none’.    success handler, authentication failure handler and logout success handler beans.
  • Configure the used authentication manager and set the use implementation of the UserDetailsService  interface. In this example we will use an implementation that stores the username and password in memory.Instead of the default handlers. We also must set a reference to the used authentication manager bean and the url that is processed by the login filter. We  also set some non mandatory properties such as usernameParameter,   passwordParameter and the postOnly parameter.The used authentication entry point bean.The default login filter.
  • Configure the used authentication manager and set the use implementation of the UserDetailsService  interface. In this example we will use an implementation that stores the username and password in memory.Instead of the default handlers. We also must set a reference to the used authentication manager bean and the url that is processed by the login filter. We  also set some non mandatory properties such as usernameParameter,   passwordParameter and the postOnly parameter.The used authentication entry point bean.The default login filter.
  • Configure the used authentication manager and set the use implementation of the UserDetailsService  interface. In this example we will use an implementation that stores the username and password in memory.Instead of the default handlers. We also must set a reference to the used authentication manager bean and the url that is processed by the login filter. We  also set some non mandatory properties such as usernameParameter,   passwordParameter and the postOnly parameter.The used authentication entry point bean.The default login filter.
  • Add a logout filter to the Spring security namespace and set the url processed by this filter.
  • Add a logout filter to the Spring security namespace and set the url processed by this filter.
  • Add a logout filter to the Spring security namespace and set the url processed by this filter.
  • Configure our permission evaluator bean.
  • Configure our permission evaluator bean.
  • Configure our permission evaluator bean.
  • Configure an expression handler bean and set a reference to our custom permission evaluator bean.
  • Configure an expression handler bean and set a reference to our custom permission evaluator bean.
  • Configure an expression handler bean and set a reference to our custom permission evaluator bean.
  • Enable the @Pre and @Post security annotations and set a reference to the used expression     handler bean. We can do this by using the global-method-security and the expression-handler    elements of the security namespace.
  • Enable the @Pre and @Post security annotations and set a reference to the used expression     handler bean. We can do this by using the global-method-security and the expression-handler    elements of the security namespace.
  • Enable the @Pre and @Post security annotations and set a reference to the used expression     handler bean. We can do this by using the global-method-security and the expression-handler    elements of the security namespace.
@Testpublic void
loginWithIncorrectCredentials(){            
mockMvc.perform(post("/api/login").contentType(MediaType.APPLICATION_FORM_URLENCODED)       .param("username","user1").param("password","password1")).andExpect(status().isUnauthorized());

}

@Test

public void loginByUsingIncorrectRequestMethod(){
mockMvc.perform(get("/api/login").param("username","user").param("password","password")) .andExpect(status().isUnauthorized());
}
@Test
public void loginWithCorrectCredentials(){
mockMvc.perform(post("/api/login")                .contentType(MediaType.APPLICATION_FORM_URLENCODED)           .param("username","user").param("password","password")).andExpect(status().isOk());
}
@Test
public void logout() throws Exception {
mockMvc.perform(get("/api/logout").with(userDetailsService("user"))).andExpect(status().isOk());
}
@ExpectedDatabase("toDoData.xml")
public void addAsAnonymous(){
mockMvc.perform(post("/api/todo").contentType(IntegrationTestUtil.APPLICATION_JSON_UTF8)   .body(IntegrationTestUtil.convertObjectToJsonBytes(added)))    .andExpect(status().isUnauthorized());
}

0 comments :

Post a Comment

©2015 coffeewidme