Outline: (1) authentication × authorization; (2) JWT and its claims; (3) the auth interface and the open routes; (4) auth-service and the credential check in account; (5) the cookie; (6) AuthorizationFilter at the gateway; (7) compose, testing and pitfalls.
Let the class answer first: checking credentials in every service multiplies the attack surface and the code.
Plain SHA-256 keeps the course simple; production uses a slow, salted algorithm (bcrypt, Argon2, Spring Security's PasswordEncoder).
Stress: downstream services never parse JWTs; they just read the id-account header.
A WebClient.builder()...build() inside filter() also works, but repeats the setup on every secured request. It is waste, not a memory leak: we measured 4 rounds, about 510 thousand requests, and the live heap after a full GC stayed flat. What grows in docker stats is the heap the JVM reserves (up to 25% of the host without a limit), not a leak.
The simulator sits on the overview (bad tokens) and in section 5 of Authorization (the page's four commands).