Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies replies
    2
  • Subscribers subscribers
    15
  • Views views
    339
  • Users 0 members are here
Related
Options

Auth Token Error

Joe Young

Hello, I'm seeing the below in my replay response.

Anyone see this before? Looks like it's a token problem ??

WWW-Authenticate: Bearer error="invalid_token", error_description="The audience 'empty' is invalid"

Thank you,

 

Joseph Young

Consultant | Test Engineering

 

 

 

 

 

  • 0  

    ,
    When I search on the error I get impression that the construction of the Bearer token is not according expectations, but it might also be related to server config.

    When you are using Web HTML/HTTP protocol, you might explore the used java script to generate the token. You might run the JS code with web_run_js() command.
    You can find here an example.

    It is not that easy to accomplish, but doable.

    You might also consider to use TruClient and stay away from most scripting details, but TC is in most cases too expensive on resources to run 200+ users concurrently.

    How to ask questions

    Reward contributions via likes or 'verified answers'

  • 0 in reply to   

    Hello, this is looking like a Header/Cookie issue but I'll know more, as I continue analyzing in Dev Tools.

    I've been fixing each request, one by one. The script is built off a HAR file.

    Thank you,

     

    Joseph Young

    Consultant | Test Engineering

     

     

     

     

     

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.