Skip to content
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

Null in header 'WWW-Authenticate'. #3062

Closed
janithcmw opened this issue Aug 13, 2024 · 1 comment
Closed

Null in header 'WWW-Authenticate'. #3062

janithcmw opened this issue Aug 13, 2024 · 1 comment

Comments

@janithcmw
Copy link

Description

The following response can be observed when an API is invoked with an empty 'Authorization' header in APIM-3.2.0. Focus on the "null" in the response header 'WWW-Authenticate'.

< HTTP/1.1 401 Unauthorized
< activityid: ecbf1006-bcf7-4cce-aa42-e8ab0fb651df
< Access-Control-Expose-Headers:
< Accept: */*
< Access-Control-Allow-Origin: *
< Access-Control-Allow-Methods: POST
< WWW-Authenticate: OAuth2 realm="WSO2 API Manager" Basic Auth realm="WSO2 API Manager" null, error="invalid_token", error_description="The access token expired"
< Access-Control-Allow-Headers: authorization,Access-Control-Allow-Origin,Content-Type,SOAPAction,apikey,testKey,Authorization
< Content-Type: application/xml; charset=UTF-8
< Date: Tue, 13 Aug 2024 13:57:14 GMT
< Transfer-Encoding: chunked

Steps to Reproduce

Steps to replicate the issue.

  1. Create an API and enable 'API Key' Application level security.
  2. Invoke the API without the header 'Authorization'
  3. You can check the response header and for further confirmation, you can check the wire logs as well.

Affected Component

APIM

Version

3.2.0

Environment Details (with versions)

No response

Relevant Log Output

No response

Related Issues

No response

Suggested Labels

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants