oauth2 authorization on portal delivering error

Hi all!

We're switching up our way of accessing our apis on our developer portal. As you can see below the authorization from our documentation is now working correctly, we're able to login and call our apis as expected.

swagger.png

10971-swagger.png

Afterwards we uploaded this documentation to the portal and after testing there we see that the same documentation is now no longer working.

portal.png

Why is this happening and how would it be possible to solve this? We're trying to give the customers access to these apis with oath2.0.

If more info is needed feel free to ask!

0 1 74
1 REPLY 1

Swagger and the Portal don't always interpret API spec documents the same way, *especially* when the specs contain errors. Validating your spec with a validation tool like https://github.com/IBM/openapi-validator is a good first step, but if this fails check out the developer console after viewing the relevant page on the portal for further troubleshooting leads.