This article explains how to map a NetWare Core Protocol (NCP) server attribute from the vendor configuration file to the RSA Authentication Manager server and how to perform a test with these attributes using the NTRadPing RADIUS test utility.
In a text editor such as Notepad++, create a file with the required attributes from the vendor dictionary file and save it as a .dct file:
ATTRIBUTE NCPS-Ip-PoolNr 261 integer r
ATTRIBUTE NCPS-Timeout 264 integer r
Login to the primary Authentication Manager Operations Console, then:
Select Deployment Configuration > RADIUS Server.
Click on the context arrow next to the primary server name and choose Manage server files.
Click on theDictionary Files tab.
Click the Add New button.
Click Choose File and browse to the NCP.dct file created in step 1.
Verify the content of the .dct by clicking on theDictionary Files tab. Scroll to the ncp.dct and from the context arrow, choose Edit.
Click Save & Restart RADIUS server.
Click on the Configuration Files tab.
Click on the context arrow next to the dictiona.dcm file and chooseEdit.
In the dictiona.dcm file, add the ncp.dct file name. The recommendation is that files be listed in the correct alphabetic order. Since the file we are adding is called ncp.dct, the example below shows it listed after nautica.dct and before netblazr..dct.
Click Save & Restart RADIUS Server.
Again on the Configuration Files tab, select vendor.ini and choose Edit.
In the vendor.ini file scroll down so that the entry below is in alphabetical order (in the example below, the new text goes between Microsoft RRAS for Windows NT and Netscreen Technologies) then add the following text:
Click Send to see the text results. A successful authentication will show as Access-Accept. Access-Reject is a failed authentication and Access-Challenge is a message showing the passcode used has an issue and is either in New PIN Mode or Next Tokencode Mode.