PEXAdmin 1.5

Web-interface to view/edit PermissionsEX data

  1. David191212
    PEXAdmin allow you to edit your PermissionsEX data from a fancy web-interface.


    home.png Group's options.png Players list.png Permissions of a player.png permissions for a group.png tools.png

    • Don't get bored anymore with PEX permissions editing commands!
    • Global overview of all permissions + preview chat prefix / suffix set
    • Edit player and groups options (default, build, ...)
    • Easily list all registered groups / players set in PEX
    • Add / Copy / Remove groups
    • Add / Copy / Remove players
    • Edit permissions
    • Get players official and offline UUIDs
    • Chat prefix maker tool
    • Protected access (letting you can configure write/readonly access)
    Live demonstration
    Login: demo
    Password: demo

    NOTE: You only have a readonly access in live demo.

    Server Requirements:
    • PHP >= 5.3
    • PDO Drivers (MySQL)
    • Apache mod_rewrite + .htaccess enabled
    • Oxygen Framework version >= 0.1.7 (Included) (latest version available at
    • PEX backend must be set to sql
    Installation / Configuration

    Webserver configuration

    PEXAdmin comes in 2 flavors:
    • If you have access to apache server's configuration, you have to setup your virtualhost in a way to let the '/' location being mapped into the 'public' folder (e.g. if all configs are ok, you won't be able to access 'Application' folder or any of it's contents from your browser). Here is a Virtualhost directive to use for example:
    Code (Text):
    <VirtualHost *:80>
       DocumentRoot /path/where/you/put/pexadmin/public
    • If you cannot modify the server configuration and only access to the folder served as root or want to install PEXadmin in a subfolder of your website, you can download the 'subfolder' version of PEXAdmin or create it by running the scripts under the subfolder-flavor folder.
    Database configuration

    As the PEXAdmin config files are all in JSON format, watch out the syntax errors! You can use tools like JSONLint to check the syntax before editing the actual file.

    You have to set your database access to let PEXAdmin handle the permissions. Open the file Application/Config/db.json, change the host/dbname and credentials according to your database' ones.

    Code (Text):
       "default": {
           "dsn": "mysql:host=localhost;dbname=minecraft;charset=utf8",
           "user": "test",
           "password": "password"
    In this sample file, the database is hosted at 'localhost' and named 'minecraft', use the same as your PEX's config.yml.

    If you set tables aliases in PermissionsEX config.yml, you have to tell the new names to PEXAdmin by editing Application/Config/pexadmin.json. In the table_aliases section you'll find a similar syntax to the config.yml to let you tell the aliases (at left (key) you have the original table name and at right (value) you can change the name according to your PermissionEX aliases configuration).

    Users access configuration

    To allow which users can connect to PEXAdmin, you have to edit the Application/Config/users.json.

    Code (Text):
           "password": "89e495e7941cf9e40e6980d14a16bf023ccd4c91",
           "role": "read"
           "password": "d033e22ae348aeb5660fc2140aec35850c4da997",
           "role": "write"
           "password": "$2y$10$iqiefC9ER6Ifw/jnOEs8ser1ETQCZ0KDCs/ylVFPnGK.OA749WDqa",
           "role": "write",
           "hashType": "bcrypt"
    Each object is a user, the key is the user's login and data is user's password and role.

    In the sample config shown above, there are 3 users (demo , admin and admin2) and their passwords are respectively 'demo', 'admin' (hashed with SHA1 algorithm). and 'admin2' (hashed with bcrypt algorithm)

    The usernames keys must be in lowercase !

    • 'read' can see all permissions / players / groups but cannot edit them
      • it can be used for people that need to know permissions nodes without being able to edit them
    • 'write' can edit all permissions / players / groups
    hashType option specify which hash algorithm was used to hash the password
    Here's the accepted value:
    • 'sha1' (default if not provided): using the sha1 algorithm
    • 'bcrypt': more robust
    • 'clear': no hash algorithm was used, password is stored as-is (This value should not be used in production and kept to let debugging / testing purposes only!)

    To get the SHA1 hash from your password, you can use one of the the online sha1 scripts, or simply run in PHP:
    Code (Text):
    echo sha1('YOUR PASSWORD');
    To get the bcrypt hash from your password, you can also use one of the the online hash scripts, or simply run in PHP:
    Code (Text):
    echo password_hash("YOUR PASSWORD", PASSWORD_DEFAULT);
    TODO list:
    • Any ideas are welcomed!

    Feel free to ask if you have any questions :)

    Icon adapted from PermissionsEx
    TomCreeper, Sinclare and Aoro like this.

Recent Updates

  1. Tool update
  2. Subfolder update
  3. Security update

Recent Reviews

  1. zR4zzer
    Version: 1.5
    Very useful tool! g
  2. Sinclare
    Version: 1.3
    This is a great interface! Installed it seemlessly (via a subfolder), edited the necessary config files and I was off to go! In the panel I love how easy it is to manage PermissionsEX. I saw this resource awhile back and was super stoked to get around to the time of using this and today was the day!
  3. papychampi
    Version: 1.3
    1. David191212
      Author's Response
      let's talk about this by PM :)