ACLs for channels

[Draven]

Would it be possible to add in a feature to support ACLs for channels instead of using passwords? This seems much more secure to me.

Instead of setting a password for a channel that can be revealed and given out, it would make more sense to allow you to select registered users that have access to the specific channel.

[m&m's]

that adds a ton of work to the server admins to set each client to be bale to get in to any channel ,,,, not something i want to do

[Draven]

Not really.. I speak in terms of a World of Warcraft Guild server I run. We want a private channel for Officers only. We have no more than 10 Officers. I would simply lick to be able to right-click the Officers channel, select ACL and see a pop-up of all users on the server listed in alphabetical order on the left side, and on the right side are the users who have access to the channel. The system would allow you to shift/ctrl click multiple people for access.

Is that so complicated for an Admin to do?

[m&m's]

dont know how many members you got in your clan but were over 100 so far and run 9 gamee servers , and new members goinging all the time so ya that sound like a pain in the a** to me

[Draven]

We have about 100 as well, but to say NO to this feature based purely on the whole clan size isn't listening to what I want. All I would like to do is have a way to manage an ACL for 10 people. I'm not saying to replace passwords, but just add ACLs along with it.

[m&m's]

I WAS GOING TO SAY LOL making more work for me than i want lol
ts3 i think 1 of the devs stated ?? there were going to be permissions on a per user & group level , but who knows there being a bit to hush hush like some one is going to steal there ideas befor they get done or something , i think there not saying becuse there not sure what can be done in c++ and will still work like what we got now , but with more added stuff , so simply said there not going to say ?

[RG_Lunatic]

Some kind of right click, select "authorize for ACL channel", select from list of channels to authorize could be implemented. Multi-select of players would make this not too difficult. De-authorization could work the same way.

=S=

Lunatic

[Fries]

eh i think its a good idea, because more then likely there will be people who can guess the passwords of chanels multiple times, or the pass is given to them, but im guess from what i think hes asking for, is to allow certain people to enter certain chanels without using a password? atleast tahts what it seems to me, correct me if im wrong please, another thing is... It would be nice if you are the admin and are able to "see" every other players messages to others such as...

(however teh messages are started?)
"[03:39:45] *==> Fred: LOL, hes such a dou***"
"[03:40:34] *==> Bob: Who? Dan?"
"[03:41:43] *==> Fred: yes dan you stupid"
"[03:42:10] *==> Bob: oh yea, he is.."
"[03:45:35] *==> Dan_leader: whats up boys? talking about me?"
"[03:49:45] *==> Fred: No we're not.
"[03:50:45] *==> Dan_leader: Hmmm thats not what i see..."
"[03:51:27] *==> Fred: i swear we're not..
*as admin dan can see what they were saying to eachother*
*dan warns them not to disrespect him anymore*
*they do and dan bans them form clan and teamspeak*

I hope this sets your guys' minds to what i was suggesting, if it hasnt been already or.. isnt already availible... because you can also see if anyone gave out passwords or is harrassing other players or anything.. well goodnight all its sleepy time...

[[BBF]Jester]

We are wanting similar functionality. Currently we are redesigning our site to integrate phpBB3 (upon release), a CMS, and with enough love in the web-administation side, TS3. We are a hoping for LDAP user/group based authentication or the ability to perform all functions on the server via web scripts.

One major feature we are looking for is to be able to tie in our site user DB into the TS users so by setting a flag on the user account, the person can log into TS then to extend that (based on how TS3 perms are done) by depending on site group membership is what permissions/rights the user will have on the server.

IOW.. a single sign on type of application. Identity management. role based security. All of the modern day management features of corporate america.

[LukeK]

Jester']We are a hoping for LDAP user/group based authentication or the ability to perform all functions on the server via web scripts.

Exactly! The whole user/group paradigm is well-understood and supported, and it's easy to configure using databases or an LDAP server. That's all we use.

One major feature we are looking for is to be able to tie in our site user DB into the TS users so by setting a flag on the user account, the person can log into TS then to extend that (based on how TS3 perms are done) by depending on site group membership is what permissions/rights the user will have on the server.

What would be nice from a database access perspective, is to have TS3 access a data source for a table or view of user names/hashed passwords, and then another table of user names/group names. You could probably set up views to selectively control what users/groups are available to TS3.

IOW.. a single sign on type of application. Identity management. role based security. All of the modern day management features of corporate america.

Exactly. These kind of features are exactly what TS3 needs to take them beyond the "ub3r gamerz" crowd and into larger-scale usage.

Cheers!

Luke

[[BBF]Jester]

Exactly. These kind of features are exactly what TS3 needs to take them beyond the "ub3r gamerz" crowd and into larger-scale usage.

Cheers!

Luke

Those are not features for TS3. TS is a single app, it just needs to provide a method for being interacted with in a standard/plugable way. SSO, IDM, etc.. that is infrastructure.

[RG_Lunatic]

What I see as absolutely necessary is some way to manage registration entirely offline.

For example, lets say I am hosting a game server for players who pay to play. I would need a way to register them for TS when they subscribe to use the server, and to remove them when they unsubscribe. Also, I would not want any visitors entry channel at all.

=S=

Lunatic

[LukeK]

Jester']Those are not features for TS3. TS is a single app, it just needs to provide a method for being interacted with in a standard/plugable way. SSO, IDM, etc.. that is infrastructure.

My point was that TS3 needs to support this. An external, industry standard mechanism (like LDAP) is a good way to do this. Right now we have nothing.

Cheers!

Luke