-
Notifications
You must be signed in to change notification settings - Fork 12
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
[Feature request] Control usernames in teamSpeak #40
Comments
As far as I know, Alliance Auth manages to exert direct control over Teamspeak users' names. Is that something SeAT could achieve? Alternatively, it doesn't seem to be too much of a security issue to have users join programmatically with their correct name rather than a uid. Caveat: Prefixes may not be as desirable for Teamspeak as they are for discord/discourse, since they can instead be set via Teamspeak group. |
Teamspeak API does not allow client user to be altered, in any way. We may implement a kick action on the update nickname flow for teamspeak, that's a working use case. But it seems a little bit hard for that poor boy, no ? |
I think it's normal. Most of big alliances use that algorithm and people are familiar with that mechanic. |
It would be great to have the option to assign the user the correct name on initial login rather than a random series of characters. This way the onus is not on the user to change their name to a perfect format. |
Yeah, it's not as "secure" but the risk seems incredibly minimal.
…On Wed, Nov 11, 2020 at 10:57 AM tribulex ***@***.***> wrote:
It would be great to have the option to assign the user the correct name
on initial login rather than a random series of characters. This way the
onus is not on the user to change their name to a perfect format.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#40 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAND332CAQ6G3B4BFXUPJF3SPKX6NANCNFSM4RMA4FOQ>
.
|
If it is an option, accepting the risk is up to the person running the service. |
ServerQuery can update the client description (clientdbedit cldbid=$ client_description=$). |
Could we have an option to have SeAT continue to authenticate how it currently does (random letters / numbers), and then when running |
@teh-banana I had spawn that at some time - but never be able to valid its flow : warlof/seat-teamspeak#25 |
Hi!
Please add nickname control mechanism to TS plugin. It can check by cron username in TS and kick users who don't meet username format requirements like discord "[%1$s] %2$s" with message "Your nickname must be [%1$s] %2$s"
Thank you!
The text was updated successfully, but these errors were encountered: