Closed
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
I've tried two OpenAPI specs:
- https://api.timechimp.com/swagger/docs/v1 (which uses
apiKey
with anAuthorization
header) - https://github.com/MicrosoftDocs/vsts-rest-api-specs/blob/master/specification/core/6.1/core.json (which uses
basic
)
No matter the values I tried, I could never get the API's to properly authenticate. Whereas if I use the plain REST API and setup the authorization headers accordingly, the endpoint work fine.
Expected Behavior
The API's actually authenticate properly depending on their type.
Steps to reproduce
Use the above OpenAPI specs, or find something else you as a developer have access to, and try to get the different types of authorization to work.
Environment
No response
Additional Information
I've tried to go through the code and see if I could spot something glaringly wrong. I couldn't, but I have a feeling the authorization headers aren't properly set on the fetch-request. That said, I will see if I can inspect it using the Inspector... Nope.
Metadata
Metadata
Assignees
Type
Projects
Status
✅ Done