<P>Alliance Account Management v February 2001<BR>Table of Contents<BR>1. BRIEF HISTORY...............................................1<BR>2. ALLOCATION AND ACCOUNT MANAGEMENT PROCESS....................1<BR>2.1. Proposal Submission and Review............................ 1<BR>2.1.1. Submitting the Proposal..................................... 1<BR>2.1.2. Reviewing the Proposal ...................................... 2<BR>2.1.3. Notifying the Principal Investigator.................... 2<BR>2.2. Establishing Access to Resources ............................ 2<BR>2.2.1. Account Created ................................................. 2<BR>2.2.2. Account Established and Logged........................ 2<BR>2.2.3. Acknowledgement and Notification .................... 2<BR>2.3. Issuing User Certificates ............................. 2<BR>2.3.1. User Request for a Certificate............................ 2<BR>2.3.2. Update grid-mapfile................................... 3<BR>2.3.3. User Notification ....................................... 3<BR>2.4. Tracking Account Usage .................................... 3<BR>2.4.1. Collection of Usage Data............................... 3<BR>2.4.2. Consolidation and Updates to Database................ 3<BR>2.4.3. Generation of Reports................................. 3<BR>2.5. Maintaining Existing Accounts............................ 4<BR>2.5.1. Modifying Existing Accounts ........................... 4<BR>2.5.2. Restricting Existing Accounts .......................... 4<BR>2.5.3. Deleting Existing Accounts ............................. 4<BR>3. DETERMINING AUTOMATION REQUIREMENTS .........................5<BR>3.1. Scalable and extensible.............................. 5<BR>3.1.1. Growing number of partner sites and resources........... 5<BR>3.1.2. Account procedures change ............................. 5<BR>3.1.3. Integration of central and local site policies and procedures ....................... 5<BR>3.2. Robust, Reliable, and Fault Tolerant..................... 5<BR>3.2.1. Improve turnaround time ............................ 5<BR>3.2.2. Increase staff productivity ............................... 5<BR>3.2.3. Limit need for human intervention ...................... 5<BR>3.2.4. Recover from outages ................................ 6<BR>3.3. Secure Data Transfer ................................... 6<BR>3.4. Support X.509 Authentication .............................. 6<BR>4. IMPLEMENTING THE REQUIREMENTS ...........7<BR>4.1. Centralized relational database............................. 7<BR>4.2. Two-way transaction model.................................... 7<BR>4.2.1. Subaccount transactions................................. 7<BR>4.2.2. Secure file transfers ............................... 8<BR>4.3. Template transaction file interpreter........................ 8<BR>4.3.1. Transaction files are parsed for requests.............. 8<BR>4.3.2. Requests use local account management procedures...................... 8<BR>4.3.3. Transaction request acknowledgements are sent .............................. 8<BR>4.4. Interaction with Certificate Authority................... 8<BR>4.4.1. CA requests verification information from central database ............................................. 8<BR>4.4.2. CA requests Distinguished Name from central database.................................... 9<BR>4.4.3. CA notifies central database upon issuance of a certificate ........................................................ 9<BR>4.4.4. Maintenance of grid-mapfile...................... 9<BR>APPENDIX A—ACCOUNT MANAGEMENT TRANSACTIONS..............10</P>
<P> <BR></P>