Membrane API Gateway returns 500 Internal Server Error when the authorization endpoint of its OAuth2 authorization server (oauth2authserver) throws an unexpected exception while processing an authorization request.
The response contains the status 500 Internal Server Error and the problem type https://membrane-api.io/problems/internal. The type internal means that the gateway failed while processing the exchange. For this error, Membrane always suppresses the details, even in development mode, so the response does not contain a detail or a link to this page.
The authorization endpoint (/oauth2/auth) validates the authorization request. Problems such as a missing client_id, an unknown client or an invalid scope are answered with regular OAuth2 error responses. This error covers unexpected failures beyond that validation.
The query string contains the same parameter more than once, for example scope twice. The parameter parser rejects duplicate keys.
The query string contains an invalid percent-encoding, or the request URI cannot be parsed.
A failure in the session manager or elsewhere in the authorization server. This is rare and usually indicates a bug in Membrane.
error level.Unlike most Membrane errors, this one never contains the detail or the link to this page, not even in development mode. Use the gateway log to find the cause.
Configuration reference:
Tutorials with runnable examples:
Still stuck? See the troubleshooting guide or ask on GitHub Issues. For commercial support, contact info@predic8.de.