Legacy Dev Forum Posts

 View Only

Sign Up

Authorization not passed to consuming action

  • 1.  Authorization not passed to consuming action

    Posted 06-05-2025 18:26

    robert.veenendaal | 2023-06-26 11:39:48 UTC | #1

    Hi, I have an API endpoint which have a content-type "x-www-form-urlencoded" for the Auth part. The result is a redacted access token: "accesstoken": "<REDACTED STRING(1286)>". . In a post API call, using this auth, I use "${authResponse.tokentype} ${authResponse.access_token}" for the Authorization header.

    This fails with a 401: "No authentication bearer token specified in authorization header." . Howeaver, when I hardcode the Autorization in the data action Bearer accesstoken (from postman), the data action runs successfully. Any ideas?


    system | 2023-07-27 11:40:07 UTC | #2

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


    This post was migrated from the old Developer Forum.

    ref: 20670