Cisco Intersight Credentials
Cisco Intersight Credentials authenticate Cisco Workflows requests to Cisco Intersight SaaS.
The adapter supports two authentication types:
-
API Key HTTP Signature: uses an Intersight API key ID and private key PEM. API key v3 uses Intersight FIPS ECDSA P-256 keys with HS2019 signing. API key v2 supports legacy RSA keys.
-
OAuth2 Client Credentials: uses an OAuth2 client ID and client secret.
Before You Begin
Create or collect the credential in Cisco Intersight. Keep private keys and client secrets secure. Do not paste them into workflow notes, comments, or logs.
For API key authentication, generate or collect the API key ID and matching private key PEM from Intersight. Use API key v3 for new FIPS ECDSA P-256 keys. Use API key v2 only for legacy RSA keys.
For OAuth2 authentication, create or collect an OAuth2 client ID and client secret from Cisco Intersight.
Adding Cisco Intersight Credentials
-
In Workflows, go to Automation > Account Keys.
-
Select New Account Key.
-
Select Cisco Intersight Credentials.
-
Enter a display name and description.
-
Select the Authentication Type.
-
Enter the required fields for the selected authentication type.
-
Select Submit.
Credential Fields
| Field | Required | Description |
|
Authentication Type |
Yes |
Select API Key HTTP Signature or OAuth2 Client Credentials. |
| API Key Version | Required for API Key HTTP Signature | Select API Key v3 (ECDSA P-256) for Intersight FIPS ECDSA P-256 API keys, or API Key v2 (RSA) for legacy RSA API keys. |
| API Key ID | Required for API Key HTTP Signature | Intersight API key identifier used for HTTP Signature authentication. |
| Private Key PEM | Required for API Key HTTP Signature | PEM private key paired with the API key. Paste the complete PEM private key, including its BEGIN and END lines, and preserve all line breaks. |
|
OAuth2 Client ID |
Required for OAuth2 Client Credentials |
Cisco Intersight OAuth2 app-registration client ID. |
|
OAuth2 Client Secret |
Required for OAuth2 Client Credentials | Cisco Intersight OAuth2 app-registration client secret. |
Notes
The signing algorithm is derived from API Key Version for new credentials. API key v3 uses ECDSA P-256 with HS2019 signing. API key v2 uses legacy RSA signing.
If target creation fails with an authentication error, verify the API key ID, API key version, private key PEM, key status, account, and expiration in Intersight.