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

'Access token' and even 'user ID and password' can be confused with turnserver.conf credentials #24

Open
reivilibre opened this issue Jan 20, 2021 · 2 comments

Comments

@reivilibre
Copy link
Contributor

@reivilibre aha, I see! I mistook "user id and password" and "access token" to be based on the nomenclature in turnserver.conf (i.e. the static-auth-secret and "user=username1:password1").

Originally posted by @rht in matrix-org/synapse#9135 (comment)

@reivilibre reivilibre changed the title @reivilibre aha, I see! I mistook "user id and password" and "access token" to be based on the nomenclature in turnserver.conf (i.e. the static-auth-secret and "user=username1:password1"). 'Access token' and even 'user ID and password' can be confused with turnserver.conf credentials Jan 20, 2021
@rht
Copy link

rht commented Jan 20, 2021

For discoverability, there could be a hover link over the "Access Token" to a page/hover-text that tells how to get the access token (e.g. "(in Riot/Web, you can look at Settings → Help & About → Access token: >click to reveal>").

@richvdh
Copy link
Member

richvdh commented Jan 20, 2021

A mode in which you specify the turn-server URL(s) and the shared secret might be useful anyway.

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

No branches or pull requests

3 participants