Forum

Results 1 to 10 of 10

Thread: Ldap / ad

  1. #1
    Join Date
    March 2010
    Location
    Iceland
    Posts
    1

    Ldap / ad

    Hi, been searching the forums but have not found any recent threads about this. Is there support for LDAP / AD authentication for ts3 ? if not is that something you guys have on your to do list ?


    Best regards,

    Changer

  2. #2
    Join Date
    January 2010
    Location
    DK
    Posts
    31
    I'm also really interested in knowing this.

  3. #3
    Join Date
    December 2009
    Location
    Germany
    Posts
    226
    Since TS3 isn't using usernames and passwords, what do you expect to get out of your directory?

  4. #4
    Join Date
    January 2010
    Location
    DK
    Posts
    31
    Well if it is added, then you can map groups to channels, limiting/granting access.

    At the moment the task is redundant, since you have to setup "groups" in AD and then do it again in TS3, plus the extra work of maintaining the TS3 member list.

  5. #5
    Join Date
    January 2010
    Location
    Secret Base in Arctic Region
    Posts
    1,671
    Another question, what does a voice-software like TS have to do with AD Domain Services?

  6. #6
    Join Date
    December 2009
    Location
    Germany
    Posts
    226
    Quote Originally Posted by TBK0000 View Post
    Well if it is added, then you can map groups to channels, limiting/granting access.

    At the moment the task is redundant, since you have to setup "groups" in AD and then do it again in TS3, plus the extra work of maintaining the TS3 member list.
    But how would you do that? Would you add the unique ID of every user into your AD? Well, no use in talking about that, it doesn't fit the current style of authentication and I hardly think the devs would use time for that.

    Quote Originally Posted by Alcazar View Post
    Another question, what does a voice-software like TS have to do with AD Domain Services?
    I guess he wanted to have users login with those credentials and have them put into the right groups at once. Good idea - if TS3 would use username/password.

  7. #7
    Join Date
    January 2010
    Location
    DK
    Posts
    31
    Quote Originally Posted by Baraan View Post
    But how would you do that? Would you add the unique ID of every user into your AD? Well, no use in talking about that, it doesn't fit the current style of authentication and I hardly think the devs would use time for that.


    I guess he wanted to have users login with those credentials and have them put into the right groups at once. Good idea - if TS3 would use username/password.

    In a way it already does, it uses a "token" to represent the user name and password aka credentials, plus if you look in the server client table you will find:
    client_login_name
    client_login_password


    If a authentication LDAP server plugin was written, then it could monitor an OU (or several) in AD and then create the users in TS, to give the user access the token to authenticate via the client (just like people do now when restoring/having reinstalled) to be emailed to them and it can also stored in a custom AD field for the admin to lookup in case of the user loosing it.


    My identity life work flow starts in AD not TS, so moving from TS to AD isn't the issue.

  8. #8
    Join Date
    January 2010
    Location
    Secret Base in Arctic Region
    Posts
    1,671
    A "token" or now called "privilege key" is not a credential nor an authentication.
    Its a random generated string that an user can use to get membership in a certain server/channel group.

    The "client_login_name" and "client_login_password" fields in _clients Table are used for ServerQuery Logins.

  9. #9
    Join Date
    January 2010
    Location
    DK
    Posts
    31
    Quote Originally Posted by Alcazar View Post
    A "token" or now called "privilege key" is not a credential nor an authentication.
    Its a random generated string that an user can use to get membership in a certain server/channel group.
    Your first statement is contradicting itself. You say it isn't a credential, but it still grants people access, and that makes is a credential.

    Quote Originally Posted by Alcazar View Post
    The "client_login_name" and "client_login_password" fields in _clients Table are used for ServerQuery Logins.

    Yes at the moment.

  10. #10
    Join Date
    January 2010
    Location
    Secret Base in Arctic Region
    Posts
    1,671
    So, if you're on your server and make an user connected to your server a member of a specific group this is a credential? Interesting.

    As for the login fields, Devs have stated several times, they wont use user/password for TS3. So these fields are for query_login only.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. LDAP - Teamspeak 3?
    By Niluan in forum Permission System
    Replies: 1
    Last Post: January 22nd, 2015, 06:19 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •