Chris Novak

Related to https://github.com/apigee/apigee-api-catalog-drupal/issues/64

Sounds like a good idea.

The documentation about this issue is now explained on the [Edge OAuthV2 Policy page, Non-RFC-compliant behavior section](https://docs.apigee.com/api-platform/reference/policies/oauthv2-policy#non-rfc-compliant-behavior).

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

Here is an [example of a RFC compliant Apigee OAuth proxy](https://github.com/kurtkanaskie/oauth-compliant) for anyone looking for a solution.

doc bug b/141752334 is now fixed.

The "SmartDocs Angular Application" is not open sourced at this time. We appreciate you wanting to help on issues like this, but at this time the code is not available...

The SmartDocs Angular application would need to be modified to allow app credentials to be sent.

"Try it now" was just released, [version 1.1](https://www.drupal.org/project/apigee_api_catalog/releases/8.x-1.1) In the meantime, you can use CSS to hide the interactivity: ``` // Remove the API Explorer .apis-explorer { display: none; }...

@boobaa can you sign the the CLA as described above? Thanks