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
Authentication headers are missing after re-disabling and re-enabling security.
{"code":"900902","message":"Missing Credentials","description":"Invalid Credentials. Make sure your API invocation call has a header: 'null : Bearer ACCESS_TOKEN' or 'null : Basic ACCESS_TOKEN' or 'apikey: API_KEY'"}
Steps to Reproduce
Create an API by disabling the security in resources(just keep only one API resource).
Disable(untick) all the application security and deploy the API.
Then re enable the security in the resource page, deploy and retry the API invocation( curl -X 'GET' \ 'https://localhost:8243/perftest/1.0' \ -H 'accept: /' \ -k).
As we checked the API definition the following header has been removed, and it causes this behavior.
x-wso2-auth-header: Authorization
Affected Component
APIM
Version
183
Environment Details (with versions)
No response
Relevant Log Output
{"code":"900902","message":"Missing Credentials","description":"Invalid Credentials. Make sure your API invocation call has a header: 'null : Bearer ACCESS_TOKEN' or 'null : Basic ACCESS_TOKEN' or 'apikey: API_KEY'"}
Related Issues
No response
Suggested Labels
APIM
The text was updated successfully, but these errors were encountered:
Description
Authentication headers are missing after re-disabling and re-enabling security.
{"code":"900902","message":"Missing Credentials","description":"Invalid Credentials. Make sure your API invocation call has a header: 'null : Bearer ACCESS_TOKEN' or 'null : Basic ACCESS_TOKEN' or 'apikey: API_KEY'"}
Steps to Reproduce
Disable(untick) all the application security and deploy the API.
Then re enable the security in the resource page, deploy and retry the API invocation( curl -X 'GET' \ 'https://localhost:8243/perftest/1.0' \ -H 'accept: /' \ -k).
As we checked the API definition the following header has been removed, and it causes this behavior.
x-wso2-auth-header: Authorization
Affected Component
APIM
Version
183
Environment Details (with versions)
No response
Relevant Log Output
Related Issues
No response
Suggested Labels
APIM
The text was updated successfully, but these errors were encountered: