If you are not using a third-party RADIUS server, you must install NMAS into your eDirectory tree. NMAS is included on the iChain Authorization Server CD under the \nmas\nmasserver directory. Change to this directory and run install.exe.
As part of the NMAS installation, you can select and install the Novell RADIUS server components. Consider the following important information:
You must install NICI 2.4.6 on the NMAS server. This version of NICI is included on the iChain Authorization Server
You should also install the NICI on the workstation where you are running ConsoleOne. The NICI files for the workstation are located on the iChain Authorization Server CD at \nici\winclient. Run the WCNICIU0 application found in this folder to install the NICI snap-ins on the workstation.
We recommend that your NMAS server reside in the same eDirectory tree as your iChain LDAP server that holds the Access Control List (ACL). Doing so allows the ACL to recognize users who are authenticating using NMAS and to allow the users access to the information they need.
If you run ConsoleOne® from a different location than the NMAS server, you must install the NMAS ConsoleOne snap-ins to that location. To do this, change to the \nmas\nmasconsoleone directory on the iChain Authorization Server CD and run snapinInstall.exe. This allows you to install the NMAS ConsoleOne snap-ins to any location you choose. Extract the RadiusSnapin.zip file into the directory where you installed ConsoleOne.
After NMAS is installed, you can select, install, and set up a third-party token login method. The token login methods are available for download at the iChain Web site. Documentation on how to install and use each token login method is provided by the partner who developed the login method.
For more information on installing and configuring NMAS and RADIUS, and for general information on installing and setting up a login method, see the NMAS product documentation on the Novell Product Documentation Web site.
For specific information on installing and using a login method, see the documentation provided by the login method partner.