Video Gaming Accessories User Manual

ManualsBrandsRSA Security ManualsVideo Gaming Accessories5.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 generation

intelligent network addressing services such as Number-Portability, Global

Title Translation, SMS/MMS/IMS/VOIP routing, and Calling Name

Presentation over a variety of C7/SS7 and IP protocols including AIN 0.2,

PCS 1900, IS41, MAP, SCCP, as well as, SIP, ENUM/DNS and

SOAP/XML.

Product Category

Networks and Communications

Summary of content (11 pages)

PAGE 1
RSA SecurID Ready Implementation Guide Last Modified: April 19, 2006 Partner Information Product Information Partner Name Web Site Product Name Version & Platform Product Description Product Category NetNumber Inc. www.netnumber.com TITAN – Transactional IP Telephony Addressing & Numbering 5.
PAGE 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.
PAGE 3
Product Requirements Partner Product Requirements: NetNumber TITAN Server CPU Memory Storage See the TITAN Installation Guide See the TITAN Installation Guide See the TITAN Installation Guide Operating System Platform Red Hat Enterprise Linux Solaris 10 Required Patches RHEL 4 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.
PAGE 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.
PAGE 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.
PAGE 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 Management link.
PAGE 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.
PAGE 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 options are shown below.
PAGE 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.
PAGE 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.
PAGE 11
Certification Checklist Date Tested: April 17, 2006 Product Name RSA Authentication Manager RSA Authentication Agent NetNumber TITAN Certification Environment Version Information Operating System 6.1 5.3 5.