API Management services API policy not applied on schema-fetch

Nicky Gottlieb Hansen 0 Omdømmepoint
2025-03-08T22:20:36.9933333+00:00

I have created a GraphQL API on my API Management Services resource in Azure.

I have configured an API policy that sets a JWT token through the "Authorization" header in the form of "Authorization": "Bearer <token_value>"

This has been added under this section:

"

Inbound processing

Modify the request before it is sent to the backend service.

"

When i go to the schema tab and press "Update from endpoint" I can see in my server logs that the JWT Bearer token was not supplied through the Authorization header, if i instead go to the "Test" tab and fire off a test GraphQL query then the Authorization header is indeed included in the request and as such the request goes through without issues.

Is this really an oversight by MS, or is there an alternative to get this working?

I would rather not have to write a custom Authorization middleware trying to validate through the request origin IP or something crazy like that on my backend service.

Microsoft Q&A
Microsoft Q&A
Brug dette mærke til at dele forslag, funktionsanmodninger og fejl med Microsoft Q&A-teamet. Microsoft Q&A-teamet evaluerer regelmæssigt din feedback og leverer opdateringer undervejs.
5 spørgsmål
{count} stemmer

1 svar

Sortér efter: Meget nyttig
  1. CamillaNrager-9308 0 Omdømmepoint
    2025-03-11T03:25:04.22+00:00
    0 kommentarer Ingen kommentarer

Dit svar

Svar kan markeres som Accepterede svar af spørgsmålsforfatteren, hvilket hjælper brugerne med at vide, at svaret løste forfatterens problem.