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

[3.2.0] Fault error response for Websocket APIs authentication error #12647

Open
chaliya96 opened this issue Mar 11, 2022 · 0 comments
Open

[3.2.0] Fault error response for Websocket APIs authentication error #12647

chaliya96 opened this issue Mar 11, 2022 · 0 comments

Comments

@chaliya96
Copy link

Description:

When invoking a websocket API in the API-Manager, APIM is returning 401 response if we do not provide the access token.

wscat -n -c wss://localhost:8099/test/1
error: Unexpected server response: 401

However if we define the access_token param in the wscat as URL parameter, we are getting different error without returning the 401.

wscat -n -c wss://localhost:8099/test/1?access_token=
error: socket hang up

Ideally with the access_token parameter also, it should return the 401 error response since no access token is provided

Steps to reproduce:

Create a sample websocket API.
Invoke it using the access_token parameter.

Affected Product Version:

v3.2.0

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

3 participants