English dropdown-ico

RSA Security 5.1 manual

1
2
3
4
5
6
7
8
9
10
11

Go to page of

Similar user manuals

A good user manual

The rules should oblige the seller to give the purchaser an operating instrucion of RSA Security 5.1, along with an item. The lack of an instruction or false information given to customer shall constitute grounds to apply for a complaint because of nonconformity of goods with the contract. In accordance with the law, a customer can receive an instruction in non-paper form; lately graphic and electronic forms of the manuals, as well as instructional videos have been majorly used. A necessary precondition for this is the unmistakable, legible character of an instruction.

What is an instruction?

The term originates from the Latin word „instructio”, which means organizing. Therefore, in an instruction of RSA Security 5.1 one could find a process description. An instruction's purpose is to teach, to ease the start-up and an item's use or performance of certain activities. An instruction is a compilation of information about an item/a service, it is a clue.

Unfortunately, only a few customers devote their time to read an instruction of RSA Security 5.1. A good user manual introduces us to a number of additional functionalities of the purchased item, and also helps us to avoid the formation of most of the defects.

What should a perfect user manual contain?

First and foremost, an user manual of RSA Security 5.1 should contain:
- informations concerning technical data of RSA Security 5.1
- name of the manufacturer and a year of construction of the RSA Security 5.1 item
- rules of operation, control and maintenance of the RSA Security 5.1 item
- safety signs and mark certificates which confirm compatibility with appropriate standards

Why don't we read the manuals?

Usually it results from the lack of time and certainty about functionalities of purchased items. Unfortunately, networking and start-up of RSA Security 5.1 alone are not enough. An instruction contains a number of clues concerning respective functionalities, safety rules, maintenance methods (what means should be used), eventual defects of RSA Security 5.1, and methods of problem resolution. Eventually, when one still can't find the answer to his problems, he will be directed to the RSA Security service. Lately animated manuals and instructional videos are quite popular among customers. These kinds of user manuals are effective; they assure that a customer will familiarize himself with the whole material, and won't skip complicated, technical information of RSA Security 5.1.

Why one should read the manuals?

It is mostly in the manuals where we will find the details concerning construction and possibility of the RSA Security 5.1 item, and its use of respective accessory, as well as information concerning all the functions and facilities.

After a successful purchase of an item one should find a moment and get to know with every part of an instruction. Currently the manuals are carefully prearranged and translated, so they could be fully understood by its users. The manuals will serve as an informational aid.

Table of contents for the manual

  • Page 1

    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.1 Product Description The NetNumber™ TIT AN server repres ents the core of a [...]

  • Page 2

    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. The RSA SecurID Agent support is seaml essly in tegrated into the TITAN application providing a sim ple deployment and configuration exp[...]

  • Page 3

    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 Operating System Platform Required Patches Red Hat Enterprise Linux RHEL 4 Solaris 10 Core OS Software Group Additional Software Requirem ents : The Java R[...]

  • 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 RS A Authenticat ion Manager database. The Agent Host record identifies the NetNumb e r TITA N se rver within its database and contain s information about communicatio[...]

  • Page 5

    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. It is assumed that the reader has both worki ng kn owledge of all products involved, a[...]

  • Page 6

    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. The followin g exam ples use the user name “qa r sa”. See the RSA documentation fo[...]

  • Page 7

    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. keyfob) in the Passcode text field and push the Sign In butto[...]

  • Page 8

    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. If the PIN is valid, the following screen is displayed instructing the user [...]

  • Page 9

    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. If the real use r then enters a correct PIN + tokencode ([...]

  • Page 10

    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. 10[...]

  • Page 11

    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.1 Red Hat Enterprise Linux 4 Mandatory Functionality RSA Native Protocol RADIUS Protocol[...]