Secure Mobile Access 12.4 Administration Guide

API Keys for Management API Access

Many modern RESTful APIs support the use of a key or token for authentication and authorization. The AMC/CMC management API currently supports username/password and API keys using HTTP BASIC authentication. This breaks down when you want to use more complex authentication for AMC, such as chained auth or SAML.

From 12.4.2 onwards, you can use API keys that allows to use the Management API without embedding user credentials in a script. API keys can be used to provide access to scripts when two-factor authentication is required for AMC access.

  • The system supports a maximum of 10 API keys per administrator.

  • The Primary Admin roles can add/remove/modify API keys for all administrators.

  • From 12.4.3, non-primary admins also can add/remove/modify their own API keys.

  • API keys cannot be assigned to administrators that are groups (local or mapped groups)

  • If the request includes both Authorization and X-API-Key headers, only the X-API-Key header will be used.

  • An API Key can optionally be made more restrictive than the role assigned to the user using Custom Permission while adding a new API Key. If the actual role becomes more restrictive, then the role permissions will take precedence and not the custom permissions.

  • The key value is displayed/returned only when:

    • Creating a new API key

    • Regenerating the value on an existing key

Was This Article Helpful?

Help us to improve our support portal

Techdocs Article Helpful form

  • Hidden
  • Hidden

Techdocs Article NOT Helpful form

  • Still can't find what you're looking for? Try our knowledge base or ask our community for more help.
  • Hidden
  • Hidden