-
-
Notifications
You must be signed in to change notification settings - Fork 971
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
Is it possible to provide a token in simple-peer opts #906
Comments
Perhaps you could implement this in your signaling layer instead? |
Hi @jzombie many thanks for getting back to me. Specifically my question relates to the following signaling server and I suspect I have to make some modifications here (they use your package), but I am unsure what I would have to do exactly. Would be terrific, if you could help me here! 😀 |
@junoriosity It is not my package. I am just advising on my own accord. With that in mind all I can do is point you to the docs here: https://nodejs.org/api/http.html#httpcreateserveroptions-requestlistener |
What version of this package are you using?
9.11.1
What problem do you want to solve?
Since we want to restrict access to our WebRTC service, we were wondering whether it would be possible to provide a token (like from Auth0 or so) via simple-peer opts (https:/feross/simple-peer#peer--new-peeropts).
However, we were unable to find out whether it is possible. Hence, it would be great if you could support us here. 😀
The text was updated successfully, but these errors were encountered: