Swagger UI console on Apigee Development portal is creating request with BearerToken instead of Bearer

Swagger UI console on Apigee Development portal is creating a request with BearerToken prefix for authorization header instead of Bearer while executing try out option on portal. Because of this token validation is failing in proxy. is there a way to change it ? or handle it in proxy ?

6304-community-question.png

0 4 531
4 REPLIES 4

You definitely shouldn't handle it in the proxy, as the OAuth specs say the token must be prefixed with Bearer.

Maybe @gkoli@apigee.com or @marshg@google.com will have seen this before?


I am having same issue as api expect Bearer prefix instead of BearerToken preifx.As per apigee docs https://docs.apigee.com/api-platform/reference/policies/oauthv2-policy#accesstokenprefixelement it specifies that only "Currently, Bearer is the only supported prefix." Is there any plan or workaround to support Bearer as well as BearerToken prefix

varuna
New Member

Any solution for this issue apart from adding javascript policy?

Not applicable