RFC 6749 / section-2.3.1

Based on RFC 6749 - The OAuth 2.0 Authorization Framework (ietf.org) in Authorization/OAuth 2.0 when we are using Client Authentication with Basic Auth header client identifier and password should be encoded in Postman

Hey @nikola.stojanovic :wave:

Welcome to the Postman Community! :postman:

What this a question or something else? Did you want to expand on the context here?

Hi,

I recently had an issue with postman with integration tests.

Library that was used added encoding in this way in Header

Base64(urlformencode(client_id) + “:” + urlformencode(client_secret)) based on Rfc6749

And postman is adding

Base64(client_id + “:” + client_secret)
based on RFC 2617

My question is: is this bug on postman or this is intended behavior?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.