Summary of the content on the page No. 1
RSA SecurID Ready Implementation Guide
Last Modified: April 19, 2006
Partner Information
Product Information
Partner Name NetNumber Inc.
Web Site www.netnumber.com
Product Name TITAN – Transactional IP Telephony Addressing & Numbering
Version & Platform 5.1
Product Description The NetNumber™ TITAN server represents the core of a communications
service providers next-generation addressing infrastructure and enables
the service provider to offer a variety of traditional and next generat
Summary of the content on the page No. 2
Solution Summary The purpose of this guide is to show an administrator how to configure the NetNumber TITAN application to use RSA SecurID to authenticate users of the web-based TITAN Administration Console. The RSA SecurID Agent support is seamlessly integrated into the TITAN application providing a simple deployment and configuration experience. The TITAN Administration Console is used to configure the settings that are necessary for the TITAN application to communicate with the RSA Authe
Summary of the content on the page No. 3
Product Requirements Partner Product Requirements: NetNumber TITAN Server CPU See the TITAN Installation Guide Memory See the TITAN Installation Guide Storage See the TITAN Installation Guide Operating System Platform Required Patches Red Hat Enterprise Linux RHEL 4 Solaris 10 Core OS Software Group Additional Software Requirements: The Java Runtime Environment, JRE, is bundled with the TITAN application distribution ensuring that the correct version is always available. Al
Summary of the content on the page No. 4
Agent Host Configuration To facilitate communication between the NetNumber TITAN and the RSA Authentication Manager / RSA SecurID Appliance, an Agent Host record must be added to the RSA Authentication Manager database. The Agent Host record identifies the NetNumber TITAN server within its database and contains information about communication and encryption. Both TITAN Master and Edge systems can be configured to be RSA Agent Hosts in order to support user authentication via RSA SecurID. T
Summary of the content on the page No. 5
Partner Authentication Agent Configuration Before You Begin This section provides instructions for integrating the NetNumber TITAN application with RSA SecurID Authentication. This document is not intended to suggest optimum installations or configurations. It is assumed that the reader has both working knowledge of all products involved, and the ability to perform the tasks outlined in this section. Administrators should have access to the product documentation for all products in orde
Summary of the content on the page No. 6
Create a TITAN Administrator There must be a user configured in both the RSA Authentication Manager and in the TITAN server who has been given the same login user name. Use the RSA Authentication Manager Administration interface to create an RSA SecurID user. The following examples use the user name “qarsa”. See the RSA documentation for detailed information on how to do this. To create a user account in the TITAN server for “qarsa”, select the System tab and then select the User Manag
Summary of the content on the page No. 7
Test Authentication of the Administrator Test that RSA SecurID authentication works by attempting to login to the TITAN application with the “qarsa” login name. Enter “qarsa” in the User Name text field and enter the tokencode displayed on their RSA SecurID authenticator (ie. keyfob) in the Passcode text field and push the Sign In button. After the first login, the user will enter their PIN followed by their tokencode into the Passcode field. A new user does not yet have a PIN until after
Summary of the content on the page No. 8
The length of the PIN is determined by the configuration settings on the RSA Authentication Manager. In the above screen, the user should make a selection by clicking on the desired button, enter a PIN if desired in the PIN and Confirm fields, and push the Ok button. If the PIN is valid, the following screen is displayed instructing the user to wait for the token code to change and then signing in with their new passcode (PIN + tokencode). The screens for the other two New PIN option
Summary of the content on the page No. 9
Next Tokencode Mode If the user enters an incorrect passcode three times, the RSA Authentication Manager puts the user into “Next Tokencode Mode”. This scenario exists to ensure that the keyfob has not been stolen/lost and that someone else is not trying to guess the PIN + tokencode. If the real user then enters a correct PIN + tokencode (passcode), the following screen is displayed: 9
Summary of the content on the page No. 10
The user should wait for the tokencode to change, enter the new tokencode in the Next Tokencode text field and then push the Sign In button. If an incorrect tokencode is entered, then the user is denied access. The next time the user tries to sign in, the user will again be prompted for the next tokencode. 10
Summary of the content on the page No. 11
Certification Checklist Date Tested: April 17, 2006 Certification Environment Product Name Version Information Operating System 6.1 Red Hat Enterprise Linux 4 RSA Authentication Manager 5.3 Red Hat Enterprise Linux 4 RSA Authentication Agent 5.1 Red Hat Enterprise Linux 4 NetNumber TITAN Mandatory Functionality RSA Native Protocol RADIUS Protocol New PIN Mode Force Authentication After New PIN Force Authentication After New PIN N/A System Generated PIN System Generated
