Red Hat 3scale API returns 403 (unauthorized) when a valid access token is used

Solution Verified - Updated -

Issue

When I execute an API call, Red Hat 3scale returns HTTP 403 (unauthorized) even when a valid access token has been used. We have confirmed the token is valid by calling another API method using the same access token and it returned HTTP 200 (OK).

Environment

  • Red Hat 3scale API Management
    • SaaS

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.