-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Combined tokens / password access #2580
Comments
Something like this
|
So, based on the findings, I think it would maybe make sense to create one validation function in the gateway (janus.c) and call it from those 2 places to prevent errors :) |
So, I wanted to test it, there is a working version here, not sure if it is correct language wise. |
The logic in the HTTP transport plugin was changed on purpose, since there was an issue documented in #2520 and fixed in #2524, which is indeed the commit you referenced to. If you think you have a fix for this, please prepare a pull request rather than linking to a branch, as that would force me to look for the changes manually. |
Closing as your PR has been merged. |
After update to 0.10.10 the streaming connection is not working.
I have api_secret enabled as it allows for token issue, which is then used for user connection.
Before the update it was working fine, now it seems that if the api_secret is set, it needs to be used with the token.
Strange behavior is that the POST request will work, but the GET will return 403.
I believe the error is located here (
janus-gateway/transports/janus_http.c
Line 1553 in 46a6c71
janus-gateway/janus.c
Line 917 in 46a6c71
Also, the POST request will eventually end up here (
janus-gateway/janus.c
Line 899 in ad54495
It was "fixed" in this commit (16173af)
I've read the issues and I don't think the fix is valid.
The proper one should be to still check if the secret/token is needed before setting the value to true.
I don't know C that much to create a PR, but if that is still needed, I can try to do so.
The text was updated successfully, but these errors were encountered: