Integrated portal api authorization issues

Hello everyone who is reading this, I've got an interesting issue for you today.

Multiple apis that we have developed have both a Basic Auth as well as a Bearer. Basic is usually used for the login to see if the user can access the api. The Bearer is the key they get from that.

Now onto the issue:

10633-untitled.png

As you can see here, the BearerAuth has been changed to Basic, even though in the subsequent swagger documentation it still says Bearer:

10634-swagger.png

Is this an issue from apigee, or am I doing something wrong?

Solved Solved
0 2 272
1 ACCEPTED SOLUTION

This is a known issue in the Integrated Portal, works fine in Spec editor.

You can workaround by using the "apiKey" type.

For example:

    FauxBearer - Paste in value - Bearer YOUR-TOKEN:
      type: "apiKey"
      name: "Authorization"
      in: "header"
      description: >-
        Workaround for Bearer scheme. Enter the following in the Key field **Bearer YOUR-TOKEN**

This is view inSpec Editor.

10637-screen-shot-2020-12-09-at-14046-pm.png

This is view in Portal

10636-screen-shot-2020-12-09-at-13951-pm.png

View solution in original post

2 REPLIES 2

This is a known issue in the Integrated Portal, works fine in Spec editor.

You can workaround by using the "apiKey" type.

For example:

    FauxBearer - Paste in value - Bearer YOUR-TOKEN:
      type: "apiKey"
      name: "Authorization"
      in: "header"
      description: >-
        Workaround for Bearer scheme. Enter the following in the Key field **Bearer YOUR-TOKEN**

This is view inSpec Editor.

10637-screen-shot-2020-12-09-at-14046-pm.png

This is view in Portal

10636-screen-shot-2020-12-09-at-13951-pm.png

Amazing, thank you!