RAdmin installation

Migrating from earlier versions

If you are migrating from an earlier version of RAdmin, see the special migration instructions.

Vasco Digipass, Yubikey and OATH token support

Vasco Digipass requires Authen::Digipass module. Yubikey support requires Auth::Yubikey_Decrypter. Support for OATH HOTP and TOTP tokens requires Imager::QRCode, Imager::File::GIF and MIME::Base32.

Quick Start

If you dont have time to read the installation instructions in the Installation and Reference manual and you have a vanilla Unix installation, here is a very brief summary of the steps required to install RAdmin on a Unix system. If you are installing on Windows, or are migrating from an earlier version of RAdmin, consult the Installation and Reference manual for detailed instructions.

  1. Install and configure a web server. We recommend Apache, but RAdmin will work with a range of other Unix web servers.
  2. Install and configure your selected SQL database server. RAdmin works with most free and commercial SQL servers.
  3. Obtain and install Perl version 5.8.8 or better.
  4. Obtain and install DBI and the DBD module for your selected database. DBD modules are available for many commercial, free and shareware RDBMSs. Both DBI and the selected DBD module may already be available with your chosen Perl distribution
  5. Unpack the RAdmin distribution with cat Radmin-x.x.tgz|gunzip -c|tar xvf -. You will need the Gnu Unix tool gunzip(1) to do this, which is available on and for most Unix systems.
  6. Check the latest patches and bug alerts for patches that might be relevant to your installation.
  7. Change to the distribution directory: cd Radmin-x.x
  8. Install the RAdmin tables for you selected database, using
    sh installXXX.sh
    where XXX is the name of your SQL server.
  9. perl install.pl
    When prompted, enter the full path names to the HTML and CGI directories for your web server. For a standard Apache installation, the default paths are OK.
  10. Check that RAdmin is working, try the List Users page. If that appears, your RAdmin system is working OK.
  11. Using the Add User page, add some test users.
  12. Configure your Radiator to use RAdmin, see the example radmin.cfg in the Radiator goodies directory.
  13. Set up web access controil and user access permissions as described in the RAdmin reference manual.
  14. Test your complete Radiator/SQL/RAdmin system.

If you have trouble

Before you post to the mailing list asking for assistance, we suggest you go through the following check list:

  1. If you have trouble downloading the software, please contact info@open.com.au.
  2. Consult the Reference Manual.
  3. Possibly consult the Migration instructions.
  4. Consult the FAQ for extra hints.
  5. Check that you are using the latest version of RAdmin. See http://www.open.com.au/radmin/downloads, use the username and password we have issued to you. Upgrade if you need to.
  6. Check whether there are any patches that address your problem. See the README in the patches directory for your revision. Apply any patches that you think you might need.
  7. If you still have the problem post to the RAdmin mailing list by mailing to radiator@lists.open.com.au (you will need to subscribe before first posting to that list) Be sure to include at least the following information:
    • A detailed description of the problem.
    • Your Radiator configuration file (remove any secrets and passwords first).
    • An extract from your Radiator log file (with Trace level of 4) illustrating the problem, or at least what is happening at the time of the problem.
    • Details of the computer type, operating system etc.
    This information helps people to understand your problem and help find a solution more quickly. If you have a support contract, you may email us at radius-support@open.com.au. Mail to this address will be ignored unless you have a support contract.