|
|
|||||||
NCCS User Administration Request Form
|
|
Concerning the NCCS Userid Policy:
You may specify a particular userid on the blanks provided. Your chosen userid, however, must follow the NCCS Userid Policy. If you would prefer, you may leave this item blank and the NCCS will assign a three-to-eight character code (based on your name) to act as your userid. |
You can only request a userid modification if you maintain your existing NCCS userid on at least one NCCS computing system both before and after your requested modification has been processed. You can not request a userid modification if you do not already have access to an NCCS computing system. If you do not have access to any NCCS computing system, you can only request a userid addition (cf. item 1a of the form). You can not request a userid modification if the modification requested would remove your NCCS userid completely from all NCCS computing systems. If you wish to remove your NCCS userid completely from all NCCS computing systems, you can only request a userid deletion (cf. item 1c of the form).
Enter your NCCS userid, and state the nature of the modification on the blanks provided. Refer, if necessary, to Section II of the form.
A request to delete a userid is a request to remove a userid completely from all NCCS computing systems. Enter the userid to be deleted on the blanks provided. For a deletion request Section II and Section III of the form are optional.
An Authentication Key Token (AKT) is an electronic security device (e.g. an RSA SecurID, a CrytoCard, etc.) used in conjunction with a userid and password to maintain the security of a computing resource. If an AKT is issued by the NCCS for use with your userid, you must return this device when you request your userid deletion.
|
Concerning the Disposition of Files of a Userid Being Deleted
Before requesting a userid deletion, all files required by the research effort should be transferred to one or more authorized users, otherwise, these files will be deleted when the userid is deleted. |
Enter an NCCS Identification Code question and answer on the blanks provided.
|
Concerning the NCCS Identification Code
The NCCS Identification Code is not a password. The NCCS Identification Code is used by the NCCS User Services Group to positively identify users when sensitive information--like a password--is discussed by telephone. You may use whatever question and answer combination you wish, however, you should provide a code that you will remember. If you can not remember the answer to your NCCS Identification Code question, you will be required to send by facsimile (fax) a new NCCS Identification Code question and answer combination with your signature via the following fax number: 301-286-1634 The signature on the fax will be verified against the signature on the your original NCCS User Administration Request Form userid addition request for access to NCCS computing resources. |
The NCCS will provide an initial temporary password for a request for a new userid, or a request to modify a userid password. The user will be notified of the password by telephone. Upon initial login each NCCS computing system will prompt the user to change the password. The user's initial password must contain eight (8) characters. At least one (1) of these characters must be numeric, and at least two (2) of these characters must be alphabetic. This initial password is valid for ninety (90) days, at which time the NCCS computing system will again prompt the user to change the password. More information concerning NCCS Password Policies is available.
Indicate how the NCCS computing systems are to be affected by this request by checking the blank under the appropriate Add or Modify column.
Concerning Access to NCCS Internal SystemsAccess to the Dell PowerEdge 1500SC (calvin), Dell PowerEdge 4400 (panini and webdev), Dell PowerEdge 1650 (troy) computing systems is currently limited to users authorized by the NCCS. Access to these systems requires the signature of a Principal Investigator of an NCCS Computational Project at item 21 of the form.
Indicate each non-NCCS computing system (i.e. for computing systems not listed at item 3 of the form), to be affected by this request by entering the node address of the system and the System Administrator responsible for the system in the blanks provided and by checking the blank under the appropriate Add or Modify column. (If necessary, use a separate sheet to include more systems.)
Indicate by node address or Internet Protocol (IP) address each system from which you will be accessing NCCS computing resources. Each address you provide must be resolvable through the Domain Name Service (DNS) (e.g. through the "nslookup," "host," or "dig" utilities) both forward and backward in order to be used to access NCCS computing resources. Static addresses (i.e. those addresses only resolved one way through the DNS) are not allowed.
Indicate the preferred shell to be used on all of the computing systems indicated at item 3 and item 4 of the form, by checking the blank under the appropriate Add or Modify column for the shell chosen.
If another shell program is specified at item 6e of the form, please be aware that it may not be available on the system(s) indicated at item 3 and item 4 of the form.
Indicate each Computational Project to be used by the userid on the computing systems indicated at item 3 and item 4 of the form. Also indicate the Last Name of the Principal Investigator for each Computational Project on the blank provided, and indicate how each Computational Project is to be affected by this request by checking the blank under the appropriate Add or Modify column.
Concerning Computational ProjectsThe computing systems indicated at item 3 of the form will require at least one NCCS Computational Project at item 7 of the form. The computing systems indicated at item 4 of the form may not require an NCCS Computational Project at item 7 of the form. You should check with their Principal Investigator(s) to determine whether to enter Computational Project(s) on the blanks provided or to leave this item blank.
The user will need to provide a copy of this request for each individual Principal Investigator authorizing access to one or more Computational Projects at item 7 of the form, in order to obtain each Principal Investigator's signature at item 21 of the form. If a Principal Investigator is authorizing the user on more than one Computational Project at item 7 of the form, the user needs to obtain only one signature for that Principal Investigator at item 21 of the form.
Enter the user's first name, middle initial, and last name. If the user has no middle initial, enter the code: NMI on the middle initial blank.
If the user prefers to use a nickname, enter the nickname.
Enter the user's area code and office telephone number. If the user has an extension on this telephone number, enter the extension number.
Enter an alternate area code and telephone number where the user may be reached during normal business hours. If the user has an extension on this telephone number, enter the extension number.
If the user has access to a fax machine, enter the area code and fax number.
For GSFC employees and contractors enter the GSFC organization code as found in The GSFC Telephone Directory. For remote users (i.e. non-GSFC employees, and non-GSFC contractors), enter the three-character organization code provided by your Principal Investigator.
For GSFC employees, enter the code: GSFC . For GSFC contractors, enter the user's company acronym as found in The Contractor Acronym Listing of the GSFC Telephone Directory. For remote users, enter the same code that was entered at item 13 of the form.
For NASA employees and NASA conractors, enter your NASA badge number and indicate the issuing NASA Center in the blanks provided. If you do not have a NASA badge, enter the code N/A .
Concerning SATERN TrainingAs indicated in the NASA Procedural Requirements (NPR) 2810.1A Security of Information Technology (IT), which became effective May 16, 2006, users of NASA systems or information must "Complete mandatory basic IT security awareness training prior to accessing NASA systems and applications and annually thereafter as long as access to NASA information or IT resources continues." (Reference Section 2.4.9.2.f.)
Each NASA facility is responsible for assuring that their employees and contractors have completed this training. If you are not associated with an organization code and on-site at the Goddard Space Flight Center or another NASA Center, in order to comply with this requirement, the NCCS has arranged for you to use the System for Administration, Training, and Educational Resources for NASA (SATERN). In order to use this Web-based training facility, please do the following:
https://satern.nasa.gov/
Your Center Location: Goddard Space Flight Center
NASA POC Name: George R. Rumney II
POC Email Address: rumney@nccs.nasa.gov
POC Phone Number: 301-286-4071
Enter the user's preferred e-mail address.
Enter the user's office address. If the address is on-site (i.e. at the GSFC), include the building and room numbers.
Enter your the country in which you were born.
Enter your current country/ies of citizenship.
If you are not a U.S. citizen, you must also submit a Name Check Request Form (NASA Form 531). While completing the Name Check Request Form please keep the following in mind:
You must sign your request in order to fulfill NASA, GSFC, and NCCS Security Policies.
You must obtain the signature(s) of the Principal Investigator(s) of the Computational Project(s) entered at item 7 of the form, and enter the date. All requests require a Principal Investigator's signature.
You will need to provide a copy of this request for each individual Principal Investigator authorizing access to one or more of his or her Computational Projects at item 7 of the form, in order to obtain each Principal Investigator's signature at item 21 of the form. If a Principal Investigator is authorizing you on more than one Computational Project at item 7 of the form, you will need to obtain only one signature for that Principal Investigator at item 21 of the form.
The NCCS will obtain the signature of William (Phil) P. Webster, Chief of the NASA GSFC Computational & Information Sciences and Technology Office, Code 606.0. His signature is required on all userid addition requests.
The NCCS will obtain the required signature from the GSFC IT Security Management. Approval by the GSFC IT Security Management is required on all userid addition requests for a user who is not a U.S. citizen.
You may return your completed NCCS User Administration Request Form (and your Certificate of Completion for those required to complete SATERN Training) to the following address:
|
NASA Goddard Space Flight Center NCCS User Services Group Mailstop 606.2 Greenbelt, MD 20771 USA |
Your completed NCCS User Administration Request Form (and your Certificate of Completion for those required to complete SATERN Training) may also be returned by facsimile (fax) via the following fax number:
| 301-286-1634 |
Requests made of the NCCS User Services Group are processed as quickly as possible, however, because requests are processed on a first-in, first-out basis, depending on the backlog, requests may take two or more working days to be completed. You will be notified when your request has been completed.
Questions, problems, comments, and suggestions concerning the NCCS should be directed to the NCCS User Services Group at the address or the fax number above, by telephone or voice-mail at:
| 301-286-9120 |
or by electronic mail (e-mail) at
| support@nccs.nasa.gov |
|
|
+ Privacy Policy and Important Notices + Sciences and Exploration Directorate + CISTO |
|
Curator: Mason Chang, NCCS User Services Group (301-286-9120) NASA Official: Phil Webster, High-Performance Computing Lead, GSFC Code 606.2 |
Last Modified:
Monday, 04-Feb-2008 10:29:22 EST
Reason for Modification:
Modified systems access information.