How to install the WiKID Community Edition 3.x
The steps needed to install the open source version of the WiKID Strong Authentication System
Requirements
- Postgresql
- Sun's Java 1.5 or 1.6 JDK
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
- Download and install the JDK. NB: You must download the version 1.5 jdk rpm! It is available from Sun's web site
- Create a symlink to your java install in /opt, if there is not one already.
- Our replication package requires compat-libstdc++-296 (and it's not yet a dependency).
- The WiKID rpms require perl-libwww-perl, ntp and system-config-date
- 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.
- Configure your box for WiKID:
# /opt/WiKID/sbin/wikidserver_config.sh
- Reboot or run:
- 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.
- Once setup, start the server
- 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:
su -c yum install postgresql postgreql-libs postgresql-jdbc postgresql-server postgresql-pl
ln -s /usr/java/jdk1.5.0_11/ /opt/java
yum install compat-libstdc++-296
# yum install ntp system-config-date perl-libwww-perl
su -c rpm -ivh wikid-*
#/opt/WiKID/conf/templates/wikid-firstboot.sh
/opt/WiKID/bin/wikidctl setupThe script will pick up your existing network settings, walk you through them and create an SSL cert for the server.
/opt/WiKID/bin/wikidctl start
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


Digg this!
Del.ico.us
Google
Yahoo bookmarks
Reddit
Spurl
Simpy
