Refer workaround to users impacted by Apigee OAuth policy returning incorrect OAuth2.0 token_type

[arunz6161]

Is your feature request related to a problem? Please describe. As described on the following community post, Apigee OAuth 2.0 Policy returns a non compliant token type causing downstream applications like SmartDocs and Swagger UI to send "Authorization" header prefixed with BearerToken.

Describe the solution you'd like Once doc bug 141752334 is fixed- we should redirect users to the same as a potential solution when they run in to problem described in the community post above.

Describe alternatives you've considered None.

Additional context None

[cnovak]

The documentation about this issue is now explained on the Edge OAuthV2 Policy page, Non-RFC-compliant behavior section.

[cnovak]

This feature will be in the next release of SmartDocs Drupal Angular application. (b/150637717

[cnovak]

Here is an example of a RFC compliant Apigee OAuth proxy for anyone looking for a solution.

[cnovak]

doc bug b/141752334 is now fixed.