Changes between Initial Version and Version 1 of newUsers


Ignore:
Timestamp:
06/02/17 13:55:06 (7 years ago)
Author:
lttoth@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • newUsers

    v1 v1  
     1= Creating New Users = 
     2Users fall into 3 basic categories: 
     3* Regular Staff and Student Employees 
     4* Consultants and VA Interns 
     5* OIT - SX accounts 
     6== Regular Staff and Student Employees == 
     7Both the old manual process for creating new employees and a description of the new process can be found in [[https://docs.google.com/document/d/1Q6XzhPsRqwO4OU4nV4f3iMLd9JNwcQq0Ft0NpApsprk/edit|UA - Role Provisioning Operations Manual]].  The old process description is useful in that it provides a listing of campus prefixes which comes in handy for Consultant and VA Work Study Banner User ID creation. 
     8 
     9The current process follows the following steps: 
     101. Security Coordinators open a Cherwell Ticket under the category Account Management.  The ticket includes: 
     11  1. Campus  
     12  1. UA ID (3xxxxxxx) 
     13  1. The user's full name 
     141. A Zuausr Administrator claims the ticket and runs the user creation script: 
     15  1. Login in as self to RPTP : ssh sx...@rptp.alaska.edu 
     16  1. Shell from home directory to PROD as ZUASUR : ssh zuausr@prod 
     17  1. From the command line run the creation script with the new user's UA ID as input 
     18    * $ zuaseed.ksh 3xxxxxxx 
     19    * Enter Y at first prompt to create the account 
     20    * Enter Y at the second prompt if there are no other new user creations pending;  step 2 can be applied to several users 
     21  1. Handle any errors that arise, commonly by informing the requesting Security Coordinator of the results 
     22    * An ID already exists for the user  
     23    * The user has transferred from one campus to another and the old ID is still for that campus 
     24    * The user has not been entered into appropriate tables by HR 
     25== Consultants and VA Interns == 
     26Consultants and VA Interns must be entered via SQL.  The data must be entered into both ztbusrh and ztbusrh_load.  For this reason, ZUAUSR administrators must be logged into SQLPLUS as zuausr@prod.  The basic template is the same, but some features of the data entered differ. 
     27* IDS Creation 
     28  * Unique Ids are determined by ZUAUSR administrators for consultants based on the initials of the first and last name of the user and one to two letters representing the company for which they work. 
     29  * VA students are determined by ZUAUSR administrators based on first, last, and middle initial as other users, adding numbers if necessary 
     30* Default Password 
     31  * Consultants do not have SSN numbers:  the letters 'cs'+ the first 8 numbers of their office phone provides the default password normally found under UID. 
     32  * VA Interns do have SSN numbers: These are queried in Banner 
     33* ZTBUSRH_MISC2 
     34  * Consultants will be identified by Department for which they work: <Last>/First Company,,UA Department 
     35  * VA Interns are categorized solely by campus:  UA<c> - VA Work Study, e.g., UAA - VA Work Study  
     36* Ending Date 
     37  * Consultant end dates are based on contract length 
     38  * VA Intern end dates are based on semesters and renewed when the student remains on staff 
     39* ZTBUSRH_USER_UID 
     40  * Consultants will not have a Banner PIDM, the key used to connect various Banner tables 
     41  * VA Students may have a PIDM and if known, may be supplied in the record creation 
     42 
     43=== Template for Consultants === 
     44Only the query for inserting into ztbusrh load is listed below.  The identical query is run for ztbusrh_load by replacing ztbusrh_load after INTO.  The following steps outline how to insert a consultant into ZUAUSR. 
     451. Determine which campus prefix is needed based on the list in [[https://docs.google.com/document/d/1Q6XzhPsRqwO4OU4nV4f3iMLd9JNwcQq0Ft0NpApsprk/edit|UA - Role Provisioning Operations Manual]]. 
     461. Login in to RPTP :  $ ssh sx...@rptp.alaska.edu 
     471. Open SQLPLUS as ZUAUSR : $ sqlplus zuausr@prod 
     481. Supply ZUAUSR password at prompt 
     491. Run the following query for both ZTBUSRH and ZTBUSRH_LOAD 
     50{{{ 
     51INSERT INTO ztbusrh<_load> 
     52( 
     53 ztbusrh_user_acct_id, ztbusrh_user_uid, ztbusrh_first_name, ztbusrh_last_name, 
     54 ztbusrh_middle_initial, ztbusrh_ssn, ztbusrh_misc1, ztbusrh_misc2 
     55) 
     56values 
     57( 
     58 user ID, -1, <first>, <last>, 
     59 <Company initials>, cs<nnnnnnn>, '-1', 'Last/First Co.,,UA Campus/Department' 
     60) 
     61}}} 
     62 
     63=== Query Template for VA Interns === 
     64Only the query for inserting into ztbusrh load is listed below.  The identical query is run for ztbusrh_load by replacing ztbusrh_load after INTO.  The following steps outline how to insert a consultant into ZUAUSR. 
     651. Login in to RPTP :  $ ssh sx...@rptp.alaska.edu 
     661. Open SQLPLUS as ZUAUSR : $ sqlplus zuausr@prod 
     671. Supply ZUAUSR password at prompt 
     681. Run the following query for both ZTBUSRH and ZTBUSRH_LOAD 
     69{{{ 
     70INSERT INTO ztbusrh<_load> 
     71( 
     72 ztbusrh_user_acct_id, ztbusrh_user_uid, ztbusrh_first_name, ztbusrh_last_name, 
     73 ztbusrh_middle_initial, ztbusrh_ssn, ztbusrh_misc1, ztbusrh_misc2 
     74) 
     75values 
     76( 
     77 user ID, -1, <first>, <last>, 
     78 <Middle>, SSN, '-1', 'Last/First Co.,,UA<c> - VA Work Study' 
     79) 
     80}}} 
     81 
     82