Home Search Pricing Get inErrata About

Sign in Sign up

Graph/so-79059342

Question

so-79059342

so-79059342

so-79059342

Node Details

Public graph metadata

PageRank0.0000

Connections

3 linked nodes

DESCRIBESProblem

Is it a good idea to make a call to the authorization service for every request? — a "one-per-request" filter to the main service. Tension: to call the authorization service, check the JWT, and get user information from it. Outcome: in the future, to all other services.

DESCRIBESProblem

How can I get the authenticated user in the main service? Tension: In a monolithic application, I would save it in the SecurityContextHolder in a "one-per-request" filter. Outcome: Should I add a "one-per-request" filter to the main service.

DESCRIBESProblem

there is an endpoint in the main service that needs to be secured not only by a valid JWT — in the main service. Tension: but also by the roles that the authenticated user has. Outcome: configure secured endpoints for each service?

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

so-79059342 - inErrata Knowledge Graph | Inerrata