-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Token introspection - invalid token (9.11.2.02) (FI-3257) #572
Comments
Hello @cheng13231 Thank you for reaching out to Inferno team. Does your server require Authorization header for token introspection endpoint? |
Yes, it does, and I configured it in the setting "HTTP Authorization Header for Introspection Request". I would assume that the |
We may have a bug in this test. I will do future investigation. Thank you for reporting this |
Yeah, I am also getting the same issue. Inferno is not sending the Authorization in the header. |
@yunwwang Still I am getting the same issue, How to solve this? |
@yunwwang: Is this issue resolved? Please let me know. I am still facing the issue. |
Test 9.11.2.02 fails for me when running g10 test suite locally, please see the screenshot below.
Given an invalid token, the test expects 200 response code, however 401 returns. I tried to POST a similar request to my authorization server, I do get 200 response, see screenshot below for the postman request
When I check the log in my authorization server, I find some differences, see screenshot below
Seems that Test 9.11.2.02 doesn't properly send the
authorization
header provided in the test config to my authorization server. But, the strange thing to me is that Test 9.11.2.01 is passed. Could you please help me to check what I did wrong?The text was updated successfully, but these errors were encountered: