Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/Compizfox/RadiusAdmin
A FreeRADIUS webinterface
https://github.com/Compizfox/RadiusAdmin
freeradius freeradius-webinterface php radius webapp webinterface
Last synced: about 2 months ago
JSON representation
A FreeRADIUS webinterface
- Host: GitHub
- URL: https://github.com/Compizfox/RadiusAdmin
- Owner: Compizfox
- License: gpl-3.0
- Created: 2015-04-27T01:02:06.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2023-03-29T18:32:47.000Z (over 1 year ago)
- Last Synced: 2024-07-03T06:33:49.982Z (3 months ago)
- Topics: freeradius, freeradius-webinterface, php, radius, webapp, webinterface
- Language: PHP
- Homepage:
- Size: 109 KB
- Stars: 78
- Watchers: 13
- Forks: 43
- Open Issues: 4
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
Awesome Lists containing this project
README
RadiusAdmin
===========
A FreeRADIUS webinterface
RadiusAdmin is a project of mine, with the intention of being a webinterface for FreeRADIUS (mainly for user/group management). RadiusAdmin is written in PHP and works by manipulating FreeRADIUS' SQL database. Naturally, this requires that you use the rlm_sql module for authorization and/or accounting.
FreeRADIUS' database consists of the following tables:
- radcheck
- radreply
- radgroupcheck
- radgroupreply
- radusergroup
In rlm_sql, the tables mentioned above are analogous to the *users* file in [rlm_files](http://freeradius.org/radiusd/man/rlm_files.html).
In addition, the rlm_sql schema includes some other tables:
- nas
- radacct
- radpostauth
These tables are meant for client (nas) management, accounting and post-authentication logging respectively. RadiusAdmin provides a frontend (in the case of accounting and post-auth, mostly statistics and reports) for these functions too. Of course, the again calls for the use of rlm_sql in those sections of FreeRADIUS config. For more info, please see [rlm_sql's documentation](http://wiki.freeradius.org/modules/Rlm_sql).
RadiusAdmin doesn't augment or replace FreeRADIUS' default SQL schema: it just needs access to the existing database and uses another database for RadiusAdmin's own data storage needs. This is done not to pollute FreeRADIUS' database with RadiusAdmin's own stuff.
### (Planned) Features
- Add, remove and edit users and groups
- Manage user-group relations
- Manage every user's or group's check and reply attributes
- Manage clients (nasses)
- Show statistics and graphs about accounting and post-auth data
### Development status
Currently, RadiusAdmin is in a very early stage. Most features are not done yet, and it is thus not ready for use.
##### 2015-6-21
Alpha 1 is released. The core framework is done. The only features that work are:
- User management
- Group management
- Reply and check attributes
### Used tools and libraries
RadiusAdmin uses the following server-side tools, languages and libraries:
- Primary language: PHP
- Database access layer: PDO
- Templating engine: Smarty
In addition, RadiusAdmin also uses the following front-end frameworks:
- Javascript library: jQuery
- Front-end framework: Bootstrap
- Bootstrap theme: Bootswatch Flatly
- Icon packs: Glyphicons and Font Awesome
### Screenshots
### Installation
#### Requirements
Since the latest version uses scalar type hinting and return type hinting, it requires PHP 7. Older versions work on PHP 5.4. RadiusAdmin depends on Smarty, and dependencies are managed using Composer.
#### Databases
RadiusAdmin needs access to 2 databases: FreeRADIUS' database and RadiusAdmin's own database. These two database don't necessarily have to reside on the same server, although the example config file assumes they do.
The schema for FreeRADIUS' database can be found in _raddb/mods-config/sql/main/*/schema.sql_. RadiusAdmin's schema is *radiusadmin.sql* and should be in this directory.
RadiusAdmin is made with MySQL in mind, but can probably work with other RDBMSs as well by editing *app/include/db.php*.
#### Instructions
Download a stable release or clone the development branch (bleeding edge!). Put them somewhere where your webserver has access to them.
Now run `composer install` in the directory containing *composer.json* to let Composer download the dependencies for you. The directory structure should now look like this:
- RadiusAdmin
- app
- public_html
- tmp
- vendor
As you might have guessed, the *public_html* directory is going to be the docroot. All the other directories shouldn't be publicly available. You webserver should have read+execute access to all 4 subdirectories. In addition, it needs write access to the *tmp* directory.
Create a database and user for RadiusAdmin and import the SQL file. Copy *app/config.php.example* to *app/config.php* and edit the file to reflect your database settings.