This page provides access to the necessary information and guidance for working with Service Principals.
Service Principals are identities, represented as code, used by applications, services, and automation tools to access specific resources. They allow developers to write code that can securely connect to Cisco AppDynamics public APIs on your
Observability Platform tenant. These API calls use Open Authentication 2.0 (OAuth2) token-based authentication.
You first need a Client ID and Secret to generate an access token. You then use the access token for API access calls into your
Observability Platform tenant.
It is best to create one Service Principal for each integration project.
OAuth 2.0 Security
OAuth2 is the industry-standard open protocol for authorization. It is a simple and standard method to provide third-party web, mobile, and desktop applications with an access token that authorizes sharing specific account information. As part of the OAuth process, the authorization server validates the credentials and returns a signed access token. You can use the token to make requests to Tenants during the token availability time frame.
Clients authenticate with the Authorization Server in accordance with Section 4.4 of OAuth2 [RFC6749].
Get an Access Token—generate and use an access token for API access calls into your
Observability Platform tenant.
Manage Service Principals—any management you perform on a chosen
Observability Platform tenant will not convey to another Tenant because they are
Observability Platform tenant-specific.
Rotate or Revoke a Secret—rotating a secret keeps two secrets valid for a period of time. Revoking a secret causes access tokens to fail authentication.
