Access Keys

In Sumo Logic, you'll need an access key to:

• Register new Collectors. When you install a Collector, in addition to having a role that grants you the Manage Collectors capability, you must supply an access key. You can use a different access key for each Collector, or use the same access key for multiple Collectors. The only time a Collector uses the access key is at installation, so if a key is deleted after a Collector has been set up, the Collector isn't affected.
• Use Sumo Logic APIs. You must supply an access key to use the Sumo Logic APIs. See API Authentication for details.

Prerequisites

• You'll need the Create Access Keys role capability to create an access key.
• You'll need the Manage Access Keys capability to manage access keys created by other users in your org.
• Access keys use the permissions of the user running the key. The user utilizing an access key must have the role capabilities needed to execute the tasks the access key is needed for.

Create an access key

From the Personal Access Keys page

1. Classic UI. In the main Sumo Logic menu, select your username and then Preferences > Personal Access Keys.
   New UI. In the top menu select your username, and then under Preferences select Personal Access Keys. You can also click the Go To... menu at the top of the screen and select Personal Access Keys.
2. On the Personal Access Keys tab, click + Add Access Key.
   
   The Add New Access Key window appears.
   
3. Name. Enter a name for your access key.
4. Allowed CORS Domains (optional). Create an allowlist of domains from which the access key can be used to access Sumo Logic APIs. For more information, see CORS support.
   note

   Enter the domains in the Origin format described in Mozilla help. The URL pattern must include the HTTPS protocol and a domain name. A port is optional.

5. Scopes. For additional security, you can select scopes to give the key only the permissions you specify.
   note

   The user who will be utilizing the access key needs to have all the same role capabilities as the scopes on the access key. Otherwise, once the user views the access key details, the scopes will be displayed as red in the UI red with a message that the user does not have rights for those scopes.

   Select the scopes for the key:
   • Default. The key has all permissions.
   • Custom. The key has only the specified permissions.
     
     Select the View and Manage permissions that you want the access key to have using the available categories.
     
6. Click Save to generate the key.
7. IMPORTANT. Copy both the generated Access ID and Access Key before clicking Done. This is the only time you will be able to copy the ID and key.
   
   warning

   After you click Done, you will not be able to recover this Access ID and Access Key.

All personal access keys created in the organization are displayed in the Access Keys page, described next.

From the Access Keys page

Administrators can create access keys under Access Keys as an alternative to doing it from the Personal Access Keys page.

1. Classic UI. In the main Sumo Logic menu, select Administration > Security > Access Keys.
   New UI. In the top menu select Administration, and then under Account Security Settings select Access Keys. You can also click the Go To... menu at the top of the screen and select Access Keys.
2. At the top right of the table, click + Add Access Key.
   
3. Follow the steps in the previous section, starting with step 3.

CORS support

Sumo Logic supports cross-origin resource sharing (CORS), a mechanism that uses additional HTTP headers to tell a browser to let a web application running at one origin (domain) have permission to access selected resources from a server at a different origin. When you create an access key, you can optionally define an allowlist of domains that may access Sumo Logic APIs using that access key. 

Whether Sumo Logic accepts or rejects an API request depends on whether it contains an ORIGIN header and the entries in the allowlist. Sumo Logic rejects:

• Requests with an ORIGIN header but the allowlist is empty.
• Requests with an ORIGIN header that do not match any entry in the allowlist.

When Sumo Logic rejects a request, it issues an httpErrorCode 403 error. The error key is "forbidden" and the error message is: The request origin is not allowlisted to use this access key.

Sumo Logic accepts:

• Requests without an ORIGIN header. 
• Requests with an ORIGIN header that matches an entry in the allowlist.
• All OPTIONS requests.

When Sumo Logic accepts a request, the response includes the ORIGIN header in an Access-Control-Allow-Origin header.

Edit, deactivate, or delete access keys

Personal access keys

1. Classic UI. In the main Sumo Logic menu, select your username and then Preferences > Personal Access Keys.
   New UI. In the top menu select your username, and then under Preferences select Personal Access Keys. You can also click the Go To... menu at the top of the screen and select Personal Access Keys.
2. Hover your mouse over an access key and click the three-dot kebab icon to reveal the modification options:
   
   • Edit. Opens up a window where you can modify the allowlist for your access key.
   • Activate/Deactivate. Depending on the current status of your access key, you'll see either an Activate or Deactivate option. If you deactivate an access key, Sumo Logic will retain the key credentials, but render the key useless. By default, Sumo Logic will deactivate an access key if it has gone unused for more than 30 days, though the Access Keys deactivation policy can be updated by a Sumo Logic administrator. You can reactivate a key at any time to begin using it again.
     note

     After an access key is deactivated, there can be a brief period of time during which a previous successful authentication remains cached and a subsequent API request using the deactivated key will succeed. This could occur if the access key was used to authenticate within 15 minutes prior to the key being deactivated.

   • Delete. Permanently removes the access key. The key will no longer be usable for API calls. However, deleting a key used to register a Collector does not affect the Collector, since the only time a Collector uses the access key is at installation.

Organization access keys

If you have the Manage Access Keys role capability, you can edit, deactivate, and delete any access keys created by other users in your organization.

1. Classic UI. In the main Sumo Logic menu, select Administration > Security > Access Keys.
   New UI. In the top menu select Administration, and then under Account Security Settings select Access Keys. You can also click the Go To... menu at the top of the screen and select Access Keys.
2. Hover your mouse over an access key and click the three-dot kebab icon. This reveals the same modification options that appear on the Personal Access Key page, as described above.

Access Keys deactivation policy

To enhance the security of your account, Sumo Logic will by default automatically deactivate access keys that haven’t been used for 30 days or more. As an extra security measure, deactivating an access key that has gone unused will ensure that forgotten keys cannot be used later to access your account.

An administrator can adjust the limit to the number of days an Access Key can go unused before being automatically deactivated. To configure this option, you must be a Sumo Logic Administrator or have the Manage organization settings role capability.

To configure the Access Keys deactivation policy:

1. Classic UI. In the main Sumo Logic menu, select Administration > Security > Policies.
   New UI. In the top menu select Administration, and then under Account Security Settings select Policies. You can also click the Go To... menu at the top of the screen and select Policies.
2. Under the Access Keys Deactivation section, select a value in the No. of Days field.
   
   note

   This section is visible to Administrators only.