Child pages
  • Metadata Signing Process
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Metadata Signing Process

The InCommon metadata signing process involves the following components and actors:

  1. The metadata signing key
  2. A Key Authority Officer
  3. A Technical Authority Officer
  4. The metadata repository

The metadata signing key is the private key used to sign InCommon metadata. The public key corresponding to the private metadata signing key is bound to the metadata signing certificate, which is stored on a secure web server (ops.incommon.org). This key pair together form the basis of the trust fabric of the InCommon Federation.

The metadata signing key is a secure offline key. It is stored on the hard drive of an offline laptop, which is kept in a safe in a secure facility with strict physical access controls.

Access to the safe itself requires both a key and a pin. A Key Authority Officer provides the key while a Technical Authority Officer knows the pin. A single individual can not be both a Key Authority Officer and a Technical Authority Officer, that is, no one person knows the location of the key and the pin.

A software process that signs and publishes metadata is run daily. This process runs on an offline laptop kept in the safe. Only a handful of individuals can initiate the software process. Collectively these individuals are known as the Technical Authority.

In the same way that a bank deposit box requires two distinct physical keys, the metadata signing process requires two human actors, a Key Authority Officer and a Technical Authority Officer. Only the Key Authority Officer can access the safe while only the Technical Authority Officer can run the software process. Both are needed to complete the metadata signing process. Each limits the actions of the other.

  • No labels