Inactive [ADMN/GEN] Whitelist v2.7 [1337]

Whitelist
Version: v2.7

This plugin allows only people on your whitelist to join the server.

Features:

• Simple and easy to use
• Whitelist is automatically reloaded when changed outsite of minecraft (e.g. with a texteditor)
• Whitelist supports console commands
• SQL support
• Support for every SQL database, that has a JDBC implementation available
• User-defined table and database layouts supported

Download Whitelist
Source Code
Donate

Changelog:
Version 2.7

• Fixed SQL injections with malformed player names (thanks to Uroz for reporting!)

Version 2.6

• Fixed null ptr exception introduced with 2.5

Version 2.5

• (Possible) fix for some SQL related errors

Version 2.4

• Improved SQL connector handling with new settings directive

Version 2.3

• Fixed an unhandled exception (thx to Puremin0rez for reporting!)

Version 2.2

• Removed TSLPC
• Support for build #415

Version 2.1

• Add/Remove commands are working in SQL mode now

Version 2.0

• Added SQL support
• Minor fixes

Version 1.9

• Support for build #287

Version 1.8

• Fixed fix for non working permissions.

Version 1.7

• Fixed non working permissions (thanks to Kainzo for reporting!)

Version 1.6

• Support for Bukkit #186 (also confirmed to work with #230)

Version 1.5

• Fixed a null pointer error.

Roadmap:

• Add permissions, once implemented in Bukkit

Installation / configuration:
Copy Whitelist.jar in your plugins folder and start your server. The plugin will create new configuration files in plugins\whitelist.
In plugins\whitelist.properties you can set the following options:

• kick-message - The message that will be displayed, when a player is kicked from the server because he is not on the whitelist
• disable-list-command - Disables the /whitelist list command.
• whitelist-admins - A comma separated list of players, who are allowed to modify the whitelist ingame.

Commands:
These commands can be used by Ops ingame or in the server console. When used with the server console don't type '/' before the command.

• /whitelist help - Shows the help ;-)
• /whitelist reload - Reloads the whitelist and it's settings
• /whitelist add [playername] - Adds a player to the whitelist)
• /whitelist remove [playername] - Removes a player from the whitelist)
• /whitelist on|off - Activates/deactivates the whitelist
• /whitelist list - Lists all whitelisted players

SQL configuration:
To support as many different database configurations as possible, Whitelist sets flexibility over simplicity.
This way virtually every existing database can be used as a base for authentification.

For the following example I will assume you are using a MySQL Database with the following configuration:

• Username: root
• Passwort: fun
• Database name: Bukkit
• Table name: tbl_names with one column named "name"

Because we are using MySQL, we need the MySQL Connector/J. It can be found here.

Now that we have the connector up and running, it is time to configure Whitelist. This is done in plugins\whitelist.properties.
1) Activate SQL mode
sql-enable=true
2) Set the correct JDBC driver. Because we are using MySQL in our example we choose:
sql-driver=com.mysql.jdbc.Driver
3) Set the connection string. It depends on the database system and layout used.
In our example it is jdbc:mysql://localhost/Bukkit?user=root&password=fun.
Because we have to escape some characters in *.propertie files, we add:
sql-driver-connection=jdbc\:mysql\://localhost/Bukkit?user\=root&password\=fun
4)We have to specify a query, that will be executed on the given database. If the query's result has at least one element, the user is allowed to access the server. There is a placeholder that will be replaced with the name of the person that is trying to join: <%USERNAME%>.
We add:
sql-query=SELECT name FROM tbl_names WHERE name\='<%USERNAME%>'
5)Optional: If /whitelist add should be available in SQL mode, we have to specify a query for it:
sql-query-add=INSERT INTO tbl_users (Id, Name, Waa, Naaa) VALUES (NULL, '<%USERNAME%>', '1', '2')
6)Optional: If /whitelist remove should be available in SQL mode, we have to specify a query for it:
sql-query-remove=DELETE FROM tbl_users WHERE Name\='<%USERNAME%>'

Help, I get a 'class not found error'
Put the following line in your whitelist.properties file: sql-driver-jar={path to the connector}
The base path is the directory your craftbukkit.jar is placed in, so if you have named the connector "mysql-connector.jar" and placed it in the same directory as craftbukkit.jar you would add
sql-driver-jar=mysql-connector.jar

I need more informations!
There is a very nice written guide by MrDylan (thx!) on using Whitelist and MySQL with SMF boards, get it here.
Thats all!