Instruction/ maintenance manual of the product 5.1 RSA Security
Go to page of 11
RSA SecurID Ready Implementation Guide Last Modified: April 19, 2006 Partner Information Product Information Partner Name NetNumber Inc. Web Site www.netnumber.c om Product Name TITAN – Transaction al IP T elephony Addressing & Num ber ing Version & Platform 5.
Solution Summary The purpose of this guide is to show an admini strat or how to configure the NetNumber TITAN application to use RSA SecurID to authenticate use rs of the web-based TITAN Administratio n Con sol e.
Product Requirement s Partner Product Requirements: Ne tNumber TITAN Serv er CPU See the TITAN Installation Guide Memory See the TITAN Installation Guide Storage See the TITAN Installation Guide Opera.
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 RS A Authenticat ion Manager database.
Partner Authentication Agent Configuration Before You Begin This section provides instruction s for int egratin g the NetNumber TITAN applicat ion with RSA SecurID Authentication. This document is not intended to su ggest optimum installation s or configurations.
Create a TITAN Administrator There must be a user configured in both the R SA Authentication Ma nage r and in the TITAN server who has been given the same login u ser name. Use the RSA Authentication Manager Administration interface to create an RSA SecurID user.
Test Authentication of the Administrator Test that RSA SecurID authenticatio n works by attem pting to login to the TITAN application with the “qarsa” login name. Enter “qarsa” in the User Name text field and enter the to kencode display ed on their RSA SecurID authenticator (ie.
The length of the PIN is determined by the config ur atio n setting s on the RSA Authentication Manager. In the above screen, the user should make a sele ction by clicking on the desired button, enter a PIN if desired in the PIN and Confirm fields, an d push the Ok button.
Next Tokencode Mode If the user enters an incorrect passcode three times, the RSA Authentication Man ager puts the user into “Next Tokencode Mode”. This sce nari o exists to en sure that the keyfob has not been stolen/lost and that someone else is not trying to guess the PIN + tokencode.
The user should wait for the tokencode to cha nge, ent er the new tokencode in the Next Token cod e text field and then push the Sign In button. If an incorrect tokencode is entered, then the use r is denied access. The next time the user tries to sign in, the user will again be prompted for the next tokencode.
Certification Checklist Date Tested: April 17, 2006 Certification Environment Product Name Version Information Operating System RSA Authentication Man ager 6.1 Red Hat Enterprise Linux 4 RSA Authentication Age nt 5.3 Red Hat Enterprise Linux 4 NetNumber TITAN 5.
An important point after buying a device RSA Security 5.1 (or even before the purchase) is to read its user manual. We should do this for several simple reasons:
If you have not bought RSA Security 5.1 yet, this is a good time to familiarize yourself with the basic data on the product. First of all view first pages of the manual, you can find above. You should find there the most important technical data RSA Security 5.1 - thus you can check whether the hardware meets your expectations. When delving into next pages of the user manual, RSA Security 5.1 you will learn all the available features of the product, as well as information on its operation. The information that you get RSA Security 5.1 will certainly help you make a decision on the purchase.
If you already are a holder of RSA Security 5.1, but have not read the manual yet, you should do it for the reasons described above. You will learn then if you properly used the available features, and whether you have not made any mistakes, which can shorten the lifetime RSA Security 5.1.
However, one of the most important roles played by the user manual is to help in solving problems with RSA Security 5.1. Almost always you will find there Troubleshooting, which are the most frequently occurring failures and malfunctions of the device RSA Security 5.1 along with tips on how to solve them. Even if you fail to solve the problem, the manual will show you a further procedure – contact to the customer service center or the nearest service center
