Skip to main content

 

Cisco Meraki Documentation

Account Keys

Manage account keys for target authentication.

Account Keys

Account keys is the term Automation uses for credentials used when communicating with targets. Account keys come in a variety of types that correspond to the types of targets that are available. Targets are not required to have account keys, but for targets that require authentication, the key type must match the target type.

Account key instances can be shared across targets and workflows. For example, if a single set of credentials can be used to access a set of target network devices, you only need to create one account key that can be used for any of the targets. When it is time to change the credentials, you can go to the Account Keys list and edit the single instance to update the credentials throughout your targets and workflows.

intro_updated.jpg

The maximum number of account keys allowed is 300 per organization.

Modern Authentication

Modern authentication is the umbrella term for a combination of authentication and authorization methods between a client and server, and improved authentication security through the use of client IDs and secrets to generate tokens. Automation uses OAuth2 Microsoft Graph Credentials for authentication with Microsoft Graph Endpoint targets to integrate with Microsoft 365 and Azure Active Directory. The OAuth2 Microsoft Graph Credentials account key establishes a token exchange with Azure Active Directory so that the user token used by the account key is refreshed through Azure Active Directory whenever necessary.

API Credentials

API credentials are different from account keys. For additional information on using API credentials in a workflow, see the HTTP Authentication Help topic.

 

 

  • Was this article helpful?