Changes between Version 7 and Version 8 of GENIFAQ


Ignore:
Timestamp:
07/14/13 22:48:45 (6 years ago)
Author:
Vic Thomas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIFAQ

    v7 v8  
    1717== Topics of Interest to Experimenters ==
    1818'''1. Why do I need certificates and keys?'''
    19      GENI experimenter tools use secure [http://xmlrpc.scripting.com XML RPC] for invoking methods on GENI Aggregates.  Your certificate is used by these aggregates to verify you have the privileges needed to perform operations such as allocating resources on these aggregates.
     19     GENI experimenter tools use secure [http://xmlrpc.scripting.com XML RPC] for invoking methods on GENI Aggregates.  Your [http://en.wikipedia.org/wiki/Secure_Socket_Layer SSL] keys and certificates represent your identity for the SSL (secure sockets layer) and [http://en.wikipedia.org/wiki/HTTP_Secure HTTPS] protocols used by the secure XML RPC.  Specifically the AM API requires authentication by means of SSL client certificates signed by a trusted GENI root.
    2020
    21      Aggregates that provide you with compute resources typically allow you to log into these resources using the [http://en.wikipedia.org/wiki/Secure_Shell Secure Shell (ssh)] protocol.  Private-public key pairs instead of passwords are commonly to authenticate ssh logins.  When an aggregate provisions a compute resource and make it available to your slice, it installs your public key on the resource.  You must make sure your ssh client is configured to find your corresponding private key when you attempt to log into your compute resources.  For more information on setting up your keys and your ssh client, see [wiki:HowTo/LoginToNodes this page].
     21     Your [http://en.wikipedia.org/wiki/Secure_Shell SSH] key (not to be confused with your SSL key) is used to log into compute resources provided by GENI aggregates.  Aggregates typically use private-public key pairs instead of passwords are commonly to authenticate ssh logins.   When an aggregate provisions a compute resource and make it available to your slice, it installs your public key on the resource.  You must make sure your ssh client is configured to find your corresponding private key when you attempt to log into your compute resources.  For more information on setting up your keys and your ssh client, see [wiki:HowTo/LoginToNodes this page].