Changes between Version 1 and Version 2 of GENIDeveloper/ToolCertificates


Ignore:
Timestamp:
03/06/14 17:14:26 (10 years ago)
Author:
tmitchel@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIDeveloper/ToolCertificates

    v1 v2  
    66
    77 1. Choose a unique name for your tool and tool instance for the tool URN. The general form is ''tool''-''instance''. For example, `portal-gpo` for the GENI Portal running at the GPO, or `genidesktop-uky` for the GENI Desktop running at the University of Kentucky.
    8   a. [ggw:GAPI_AM_API_DRAFT#ToolCertificates Specifics about allowed characters, maximum lengths, etc.]
     8  a. [wiki:GAPI_AM_API_DRAFT#ToolCertificates Specifics about allowed characters, maximum lengths, etc.]
    99 1. Choose an email address for administrators of your tool. This will probably be an email list but could be the email address of an individual.
    1010 1. Create a certificate signing request
    … …  
    1717openssl req -batch -new -key PRIVATE_KEY_FILE -out CSR_FILE
    1818}}}
    19  1. [http://groups.geni.net/syseng/newticket?cc=gpo-sw-dev@geni.net&summary=Sign%20CSR%20for%20TOOL%20at%20INSTANCE Create a ticket] requesting a tool certificate
     19 1. [/geni/newticket?cc=gpo-sw-dev@geni.net&summary=Sign%20CSR%20for%20TOOL%20at%20INSTANCE Create a ticket] requesting a tool certificate
    2020  a. Edit the summary to say something like "Sign CSR for YOUR_TOOL at YOUR_INSTANCE"
    2121  a. Include the unique name (tool and instance) in the description