Return HTTP 403 when JWT is valid but missing required claims #1640
      
        
          +237
        
        
          −32
        
        
          
        
      
    
  
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Summary
Changes
MissingRequiredClaimExceptionfor handling missing required JWT claimsAuthMetadataReaderto set HTTP 403 status and WWW-Authenticate header when required claims are missingRestBridgeVerticleto preserve 403 status code (previously overridden to 400)Behavior
Before: Valid JWT with missing required claims returned 200 OK with GraphQL error
After: Valid JWT with missing required claims returns 403 Forbidden
Response Format
Test Coverage
givenJwt_whenMissingRequiredClaims_thenReturns403givenJwt_whenMissingRequiredClaimsRest_thenReturns403givenJwt_whenMissingRequiredClaimsMcp_thenFails