July 2017
Beginner to intermediate
340 pages
7h 43m
English
Even if you're doing a good job at protecting your application from bad behaviors induced by incoming data, you should also make sure the application itself is not able to do some damage in your microservice ecosystem.
If your microservice is authorized to interact with other microservices, these interactions should be authenticated, as we've seen earlier in this chapter, but also limited to the strict minimum allowed. In other words, if a microservice is performing some read calls on another microservice, it should not be able to do any POST call and restricted to read-only.
That scope limitation can be done with the JWT tokens by defining roles (such as read/write) and adding that information in the token ...
Read now
Unlock full access