You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on your first photo, it looks like there's a space in the Token input before the Response => Body Attribute tag.
The current behavior that you're showing here may be intentional; however, I can't think of a case where having a leading/trailing space would be useful.
I'll submit a pull request for review; if this behavior is intentional, please feel free to provide further feedback.
Expected Behavior
Chaining requests in order to get a bearer token from an ROPC-request. It should be able to return the token and fill it into
Authorization: Bearer
.Actual Behavior
The token generation and passing works, but the formatting in the headers seems to be wrong.
Returns this header
which yields a
401
.here you can see an extra space is added.
When filling in the same token statically, the call will work.
Reproduction Steps
Response => Body Attribute
as Token.Authorization: Bearer
Is there an existing issue for this?
Additional Information
No response
Insomnia Version
2023.2.2
What operating system are you using?
Windows
Operating System Version
Windows 11 Pro 22H2
Installation method
download from insomnia.rest
Last Known Working Insomnia version
No response
The text was updated successfully, but these errors were encountered: