Credentials for the LaunchKey API are based on items in the Admin Center. API credentials are based on an
entity (Organization, Directory, or Service) using it's ID and a valid Public Key. These items are provided in the
Authorization credentials. More information on providing credentials can be found in
Authorization and Validation.
Rotation of Public Keys is part of the core security functionality within the LaunchKey API. The Admin Center
provides the facilities for migrating one or more Public Keys to another Public Key, of set of Public Keys. Public Keys
may have expiration dates and well as being set inactive. This allows you to determine the rotation strategy you prefer.
If your security model requires the use of separate credentials for different security zones or different hardware,
the LaunchKey API supports this functionality. You can have multiple active Public Keys for the same entity.
To reduce the number of keys y9our application needs to manage, the LaunchKey API provides a hierarchical structure
in which you may provide the credentials for one the the entity's ancestors when providing credentials. The details
of providing the credentials can be found in Authorization and Validation.
A scenario in which you may want to use credential hierarchy is when you have an application suite with multiple
applications for which you prefer to segment out authorization, You can create a separate Service for each
application under a common Directory and use the credentials from the Directory to perform authorizations.
LaunchKey links to user contributed code as a resource to its community. LaunchKey does not in any way
guarantee or warrant the quality and security of these code bases. User contributed code is supported by the
creators. If you do find a link from the site to user contributed code that is malicious or inappropriate in any
way, please report that link to LaunchKey immediately and we will investigate the claim. Submit any issue to
LaunchKey support at https://launchkey.com./support.