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

Mod doesn't work with TeamSpeak 3.1.3 #29

Closed
jhakonen opened this issue Mar 26, 2017 · 5 comments
Closed

Mod doesn't work with TeamSpeak 3.1.3 #29

jhakonen opened this issue Mar 26, 2017 · 5 comments
Labels
Milestone

Comments

@jhakonen
Copy link
Owner

TeamSpeak 3.1.3 has an updated ClientQuery plugin. The plugin now requires applications (like TessuMod) to authenticate using an API key. The API key is shown in ClientQuery plugin's settings.

For more info see the release annoucement:
http://forum.teamspeak.com/threads/130474-TeamSpeak-Client-3-1-3-released

Bug reported by Grumpelumpf and Dyme.

@jhakonen jhakonen added the bug label Mar 26, 2017
@jhakonen
Copy link
Owner Author

When connecting to ClientQuery (with e.g. PuTTY; connection type: telnet, hostname: localhost, port: 25639) the welcome message has changed. There is a new line about authentication:

TS3 Client
Welcome to the TeamSpeak 3 ClientQuery interface, type "help" for a list of commands and "help <command>" for information on a specific command.
Use the "auth" command to authenticate yourself. See "help auth" for details.
selected schandlerid=1

Authentication help:

help auth
Usage: auth apikey={string}

Authenticates connecting application with API key of user.

Example:
   auth apikey=AAAA-BBBB-CCCC-DDDD-EEEE
   error id=0 msg=ok

error id=0 msg=ok

Trying any command other than auth or help before authentication ends up to an error:

use schandlerid=1
error id=1796 msg=currently\snot\spossible

Providing invalid authentication key gives following error:

auth apikey=gdfgdfgdfg
error id=1538 msg=invalid\sparameter

Providing valid key (copied from ClientQuery's settings) succeeds:

auth apikey=FB31-1LF0-24XI-K7TZ-GZ1X-7UWH
error id=0 msg=ok

After authentication other commands start to work as expected:

use schandlerid=1
selected schandlerid=1
error id=0 msg=ok

jhakonen added a commit that referenced this issue Mar 26, 2017
 - Added settings option for the API key ([TSClientQueryService] -> api_key).
 - Added notification which gives instruction of where to get the key and where to set it.
 - Added notification which lets user know when the authentication is ok.
 - Added low level ClientQuery support for the authentication.
@jhakonen
Copy link
Owner Author

The fix includes a notification which asks user to set the API key:
premission-needed

When the mod has succesfully authenticated there will be another notication to let user know that the authentication was ok:
permission-granted

@jhakonen
Copy link
Owner Author

Should really make this into a dialog of some kind which would allow user to enter the API key into a text input field, but for that I would need tools in issue #21, so that has to wait for 0.7 version.

@balexandre
Copy link

Just to provide a better info to all that want to find the API Key:

in TeamSpeak choose Tools > Options and then

@jhakonen jhakonen added this to the Release 0.7 milestone Apr 26, 2017
@jhakonen
Copy link
Owner Author

jhakonen commented Aug 6, 2019

I ended up discarding the old 0.7 development, and made a new 0.7 based on 0.6-fixes branch. As such I need to rethink how to create the dialog for inputting the API key. I'll close this issue for now.

@jhakonen jhakonen closed this as completed Aug 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants