SecuredNetwork's logo

SecuredNetwork v

1. Installation:

Download the latest version of the plugin available from the official plugin page on SpigotMC. Put the .jar file into the plugins folder of all your servers (backend and proxy servers) and restart them.

2. Generating a new passphrase:

Each player has his data representation called GameProfile. This object contains data such as the player UUID, or properties. Properties are used to store skin textures (if the server is in online-mode). These properties are then forwarded to the backend server by the proxy. On the proxy, SecuredNetwork inserts a passphrase into these properties. Backend servers then verify it and if the configured passphrase and the received one equal, the connection is accepted.
Therefore, the passphrase should be unique and completely random. Open the console on any of your proxy servers and use command /sn generate <length>. The length argument indicates the length of the newly-generated passphrase. It should be greater than 0 and the longer the new passphrase is, the better. In fact, there's no upper limit on this value, but don't enter too big, like 1000000000 or so, as it will take longer for slower connections to login (every character of the passphrase is 1 byte, a length of 1 million characters is 1MB of traffic). Recommended value is 1000. The generated passphrase was automatically saved into the config.yml file of SecuredNetwork.

3. Applying the passphrase:

The command also prompted you to reload to apply the passphrase now. We will do it later. Now, open the config.yml file of the plugin and copy the passphrase located under property.value. Then, paste the passphrase into property.value in all config.yml files of SecuredNetwork plugin (on all proxy and backend servers). Simply make sure, that property.value fields equal in all config.yml files. To apply the passphrase, run /sn reload on all your servers.

4. The second passphrase:

This step is completely optional. As properties are identified by their names and store a value (passphrase is the value), this option is also configurable in all config.yml files under property.name. If you want, you can use this as the second passphrase. Just, make sure all property.name fields in all config.yml files equal and reload all plugins again.

5. IP-whitelisting:

This step is completely optional. If you want to restrict the players to use only your domain, not the numeric IP, etc., you can, thanks to the IP-whitelisting feature.

Each player connecting with any of these IPs will be allowed to connect, others will get disconnected during the logging in process. You can whitelist number-IPs, domains, hostnames and ports. At first, set enabled: to true in the config.yml file of SecuredNetwork on the proxy to enable the IP-whitelist feature. Then, whitelist IPs by adding them to ips list following these rules:

If you have more than one proxy, replicate the process for each of them. Additionally, don't forget to run /sn reload on all your proxy servers.

6. Finish:

Congratulations, you have finished the setup process of SecuredNetwork plugin.