You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the publisher on artifacts extrated from a source APIM instance it randomly exit with an error related to the impossibility todownload the well-know configuration from URL specificed in the validate-jwt policy defined on products. The problem happens regardelss of the product being published
Expected behavior
APIs and Products are deployed successfully to the targe APIM instance
Actual behavior
The publisher randomly exit wirth the following error
Unhandled exception. System.Net.Http.HttpRequestException: HTTP request to URI https://management.azure.com/subscriptions/************/resourceGroups/********/providers/Microsoft.ApiManagement/service/*********/products/*********/policies/policy?api-version=2024-05-01 failed with status code 400. Content is '{"error":{"code":"ValidationError","message":"One or more fields contain incorrect values:","details":[{"code":"ValidationError","target":"validate-jwt","message":"Error in element 'validate-jwt' on line 40, column 4: Unable to obtain configuration from: 'https://login.microsoftonline.com/****/v2.0/.well-known/openid-configuration'. Will retry at '1/1/0001 12:00:00 AM +00:00'. Exception: 'System.IO.IOException: IDX20804: Unable to retrieve document from: 'https://login.microsoftonline.com//v2.0/.well-known/openid-configuration'.
Reproduction Steps
Publish one or more products with validate-jwt policy
Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.
Activity
github-actions commentedon May 20, 2026