anchor.diff:  
   Now when we fire up the servers everything is working and the requests are being proxied through the UI (API Gateway) to the resource server.
   
  -=== Further Simplifications
  +//=== Further Simplifications
  +=== さらなる簡略化
   
   Even better: we don't need the CORS filter any more in the resource server. We threw that one together pretty quickly anyway, and it should have been a red light that we had to do anything as technically focused by hand (especially where it concerns security). Fortunately it is now redundant, so we can just throw it away, and go back to sleeping at night!
   
  -== Securing the Resource Server
  +//== Securing the Resource Server
  +== リソースサーバをセキュアにする
   
   You might remember in the intermediate state that we started from there is no security in place for the resource server. 
   
  
positive.code: 
  That's enough to get us a secure resource server, but it won't get us a working application yet, for the same reason that it didn't in <<_the_resource_server_angular_js_and_spring_security_part_iii,Part III>>: there is no shared authentication state between the two servers.
  
  == Sharing Authentication State
  
  We can use the same mechanism to share authentication (and CSRF) state as we did in the last, i.e. https://github.com/spring-projects/spring-session/[Spring Session]. We add the dependency to both servers as before:
  
  
negative.code: 
  As long as redis is still running in the background (use the https://github.com/dsyer/spring-security-angular/tree/master/proxy/fig.yml[`fig.yml`] if you like to start it) then the system will work. Load the homepage for the UI at http://localhost:8080[http://localhost:8080] and login and you will see the message from the backend rendered on the homepage.
  
  //== How Does it Work?
  == どうやって動いているの?
  
  What is going on behind the scenes now? First we can look at the HTTP requests in the UI server (and API Gateway):
  
  