[Feature request] Control usernames in teamSpeak

[tigranm75]

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!

[Nfinished]

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.

[warlof]

Teamspeak API does not allow client user to be altered, in any way.
Also, adding a specific rule for a driver would impact other driver, which is not expected.

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 ?

[tigranm75]

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.

[tribulex]

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.

[Nfinished]

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> .

[tribulex]

If it is an option, accepting the risk is up to the person running the service.

[akturis]

ServerQuery can update the client description (clientdbedit cldbid=$ client_description=$).
The plugin can save the username with tag there.

[teh-banana]

Could we have an option to have SeAT continue to authenticate how it currently does (random letters / numbers), and then when running seat-connector:apply:policies drop server groups if the users nickname does not match the specified format. Having an option specific for TeamSpeak for this to be on/off would be ideal for people who want to continue using it as is.

[warlof]

@teh-banana I had spawn that at some time - but never be able to valid its flow : warlof/seat-teamspeak#25