Add support for TURN static auth secret credentials #3796
+38
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
hans-fritz-pommes
approved these changes
Oct 30, 2025
There was a problem hiding this comment.
I see no problem. If there is an "secret:" in the turn_server section of the config.yaml, credentials generated out of this secret are used. Otherwise "username" and "credential" are left the old values.
Found someone doing the same here: https://stackoverflow.com/questions/64362321/webrtc-coturn-authentication-using-turn-rest-api-flag-use-auth-secret-based
|
But I think you forgot to commit your change to the |
JadedBlueEyes
force-pushed
the
jade/turn-static-secret
branch
from
d2bedb3 to
287cf0a
Compare
Author
|
Image based on this branch at |
|
Would it be difficult for you to add an arm64-image? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #2245