Requirements
Hardware Requirements
- 8+ gigs of hard drive space.
- 1 gig of RAM
- 2 Ethernet connenctions
- Moderate CPU required
- These hardware specs are for production. The server has been tested in a 256 meg RAM vmware image.
Doing the work
Please note that with the 3.x versions we have moved the commands
from generic "start" and "stop" to "wikidctl start", "wikidctl stop",
"wikidctl setup" etc.
- Install Postgresql and related
su -c yum install postgresql postgreql-libs postgresql-jdbc postgresql-server postgresql-pl
- Download and install the JDK. You can download the JDK from the Java site. Be sure to download the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files or else the certificate generation will not work.
- Make sure that alternatives has the correct Java:
/usr/sbin/alternatives --install /usr/bin/java java /usr/java/latest/bin/java 2
/usr/sbin/alternatives --config java
- Test that the system is using the correct Java:
java -version
- Our replication package requires compat-libstdc++-296 (and it's not yet a dependency).
yum install compat-libstdc++-296
- The WiKID rpms require perl-libwww-perl, ntp and system-config-date
# yum install ntp system-config-date perl-libwww-perl
- Download the WiKID rpms from Sourceforge and install them. You will need both the wikid-server-community-3.0.0beta rpm and the wikid-utility rpm.
su -c rpm -ivh wikid-*
- Configure your box for WiKID:
# /opt/WiKID/sbin/wikidserver_config.sh
- Reboot or run:
#/opt/WiKID/conf/templates/wikid-firstboot.sh
- Setup the WiKID server. The WiKID token clients communicate with
the WiKID via port 80 (https is not needed because the PINs and OTPs
are asymmetrically encrypted, so you will need a routable IP address.
If you are just testing, then just make sure that the PC running the
client can get to the server.
/opt/WiKID/bin/wikidctl setup
The script will pick up your existing network settings, walk you through them and create an SSL cert for the server.
- Once setup, start the server
/opt/WiKID/bin/wikidctl start
- Go to https:///WiKIDAdmin/ to complete the set up. From here, you can follow the standard documentation. If you like short docs, I recommend the Quickstart Cheatsheet:
More Information
You may need to install the JCE Unlimited Strength Jurisdiction Policy Files to avoid the "Illegal Key Size error".
The WiKID token clients require port 80. You can use NAT, but it
needs to be routable for the token clients. The following services may
only need internal access based on your needs:
- The WiKIDAdmin uses 443.
- wAuth uses 8388
- LDAP uses 10389
- TACACS+ uses 49
Disclaimer
We test this stuff on our own machines, really we do. But you may
run into problems, if you do, come to #fedora on irc.freenode.net
Added Reading
starting tacacs
/opt/WiKID/bin/tac_plus -C /opt/WiKID/private/tacacs.conf