In a microservice architecture, a developer notices that the JWT token is forwarded but downstream services reject it. What is the most probable bug?

medium📝 Analysis Q7 of 15

Microservices - Authentication and Authorization

AThe token is forwarded without the 'Bearer' prefix in the Authorization header

BThe token is forwarded in the Cookie header instead of Authorization

CThe token is forwarded as a query parameter

DThe token is forwarded with extra spaces around it

Step-by-Step Solution

Solution:

Step 1: Understand token format requirements
Downstream services expect the Authorization header to start with 'Bearer ' followed by the token.
Step 2: Identify why missing 'Bearer' causes rejection
Without 'Bearer', the token format is invalid and services reject it.
Final Answer:
The token is forwarded without the 'Bearer' prefix in the Authorization header -> Option A
Quick Check:
Missing 'Bearer' prefix causes token rejection [OK]

Quick Trick: Include 'Bearer' prefix in Authorization header [OK]

Common Mistakes:

MISTAKES

Master "Authentication and Authorization" in Microservices

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Microservices Quizzes