'problem+json' error format

[janz93]

All our APIs are protected via oauth2 and we make use of this gem.

The OAuth2::Error class is expecting the error response to always have an error, error_description parameter

Our APIs make use of the problem+json as a structured format for error messages.

I was reading through the oauth2 spec and if I understood the spec correctly it says that the resource error response format can look however you want it to be.

Maybe it would be great to support different error formats like problem+json

PS. All thanks for the hard work that goes into this gem ❤️

[pboling]

Interesting idea. I would have guessed, based solely on your description that "error response format" would be referring to the content and format of the response body, rather than the CONTENT_TYPE. I would need to review the spec to understand what the requirements are for CONTENT_TYPE.

[janz93]

Ah my bad if it was a bit misleading 😅

Sure, let me know if I can assist you somehow.

[pboling]

@janz93 I don't understand the issue you are describing. According to https://datatracker.ietf.org/doc/html/rfc6749#section-5.2, when there is an error, the parameter error in the response is required. error_description is optional. What are you proposing that we change? What specifically is the issue you are running into?

[pboling]

Can you create a PR with a spec showing the change you would like to see?

[janz93]

After looking at the Problem again I see that my initial idea is very complicated
I think adding the problem+json to the JSON parser would be sufficient enough.
This way the error.response.parsed attribute can be used which makes the handling of the error fairly easy.

[pboling]

Support for problem+json was added by @janz93 in #553

[pboling]

@janz93 It has been released in version 2.0.0.rc1. Please try it out!