Skip to main content

1Password Source

Thumbnail icon

The 1Password Source provides a secure endpoint to receive Sign-in Attempts and Item Usage from the 1Password Event API. It securely stores the required authentication, scheduling, and state tracking information.

The 1Password Source ingests:


  • JSON is the only supported log format.
  • Data is collected in five minute intervals.


You need a 1Password API token and your customer specific 1Password domain, for example

To generate a 1Password API token follow these steps:

  1. Sign in to your 1Password account and click Integrations in the sidebar.
  2. Choose the Events Reporting integration where you want to issue a token and click Add a token.
  3. Enter a name for the bearer token and choose when it will expire. Select or deselect the event types the token has access to, then click Issue Token.
  4. Click Save in 1Password and choose which vault to save your token to. Then click View Integration Details.


A 1Password Source tracks errors, reports its health, and start-up progress. You’re informed, in real-time, if the Source is having trouble connecting, if there's an error requiring user action, or if it is healthy and collecting by utilizing Health Events.

A 1Password Source goes through the following states when created:

  1. Pending. Once the Source is submitted, it is validated, stored, and placed in a Pending state.
  2. Started. A collection task is created on the Hosted Collector.
  3. Initialized. The task configuration is complete in Sumo Logic.
  4. Authenticated. The Source successfully authenticated with 1Password.
  5. Collecting. The Source is actively collecting data from 1Password.

If the Source has any issues during any one of these states, it is placed in an Error state.

When you delete the Source, it is placed in a Stopping state. When it has successfully stopped, it is deleted from your Hosted Collector.

On the Collection page, the Health and Status for Sources is displayed. Use Health Events to investigate issues with collection. You can click the text in the Health column, such as Error, to open the issue in Health Events to investigate.
1password state.png

Hover your mouse over the status icon to view a tooltip with details on the detected issue.

Create a 1Password Source

When you create a 1Password Source, you add it to a Hosted Collector. Before creating the Source, identify the Hosted Collector you want to use or create a new Hosted Collector. For instructions, see Create a Hosted Collector.

To configure a 1Password Source:

  1. In Sumo Logic, select Manage Data > Collection > Collection.
  2. On the Collectors page, click Add Source next to a Hosted** **Collector.
  3. Select 1Password.
  4. Enter a Name for the Source. The description is optional.
  5. (Optional) For Source Category, enter any string to tag the output collected from the Source. Category metadata is stored in a searchable field called _sourceCategory.
  6. Forward to SIEM. Check the checkbox to forward your data to Cloud SIEM Enterprise. When configured with the Forward to SIEM option, the following metadata fields are set:
Field NameAPIValue
_siemVendorSign-in, Item1Password
_siemProductSign-in, Item1Password
_siemFormatSign-in, ItemJSON
  1. (Optional) Fields. Click the +Add link to add custom log metadata Fields.
    • Define the fields you want to associate, each field needs a name (key) and value.
      • green check circle.png A green circle with a check mark is shown when the field exists and is enabled in the Fields table schema.
      • orange exclamation point.png An orange triangle with an exclamation point is shown when the field doesn't exist, or is disabled, in the Fields table schema. In this case, an option to automatically add or enable the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo that does not exist in the Fields schema or is disabled it is ignored, known as dropped.
  2. Base URL. Provide your 1Password customer-specific domain, for example
  3. API Token. Enter the token you got from creating your 1Password API token in the Authentication section above.
  4. Supported APIs to collect. Select one or more of the available APIs, Item Usage and Sign-in Attempts.
  5. When you are finished configuring the Source, click Submit.

Error types

When Sumo Logic detects an issue it is tracked by Health Events. The following table shows the three possible error types, the reason the error would occur, if the Source attempts to retry, and the name of the event log in the Health Event Index.

TypeReasonRetriesRetry BehaviorHealth Event Name
ThirdPartyConfigNormally due to an invalid configuration. You'll need to review your Source configuration and make an update.No retries are attempted until the Source is updated.Not applicableThirdPartyConfigError
ThirdPartyGenericNormally due to an error communicating with the third party service APIs.YesThe Source will retry for up to 90 minutes, after which it quits.ThirdPartyGenericError
FirstPartyGenericNormally due to an error communicating with the internal Sumo Logic APIs.YesThe Source will retry for up to 90 minutes, after which it quits.FirstPartyGenericError

Restarting your Source

If your Source encounters ThirdPartyConfig errors, you can restart it from either the Sumo Logic UI or Sumo Logic API.


To restart your source in the Sumo Logic platform, follow the steps below:

  1. Open the Collection page, and go to Manage Data > Collection > Collection.
  2. Select the source and click the information icon on the right side of the row.
  3. The API usage information popup is displayed. Click the Restart Source button on the bottom left.
  4. Click Confirm to send the restart request.
  5. The bottom left of the platform will provide a notification informing you the request was successful.


To restart your source using the Sumo Management API, follow the instructions below:

  • Method: POST
  • Example endpoint:{collector_id}/sources/{source_id}/action/restart

Sumo Logic endpoints like are different in deployments outside us1. For example, an API endpoint in Europe would begin A service endpoint in us2 (Western U.S.) would begin For more information, see Sumo Logic Endpoints.

JSON configuration

Sources can be configured using UTF-8 encoded JSON files with the Collector Management API. See how to use JSON to configure Sources for details.

configJSON ObjectYesContains the [configuration parameters](#config-parameters) for the Source.
schemaRefJSON ObjectYesUse {"type":"1Password"} for a 1Password Source.not modifiable
sourceTypeStringYesUse Universal for a 1Password Source.not modifiable

Config parameters

The following table shows the config parameters for a 1Password Source.

nameStringYesType a desired name of the Source. The name must be unique per Collector. This value is assigned to the metadata field _source.modifiable
descriptionStringNonullType a description of the Source.modifiable
categoryStringNonullType a category of the source. This value is assigned to the metadata field field _sourceCategory. See best practices for details.modifiable
fieldsJSON ObjectNoJSON map of key-value fields (metadata) to apply to the Collector or Source. Use the boolean field _siemForward to enable forwarding to SIEM.modifiable
base_urlStringYesProvide your 1Password customer-specific domain, such as,
api_tokenStringYesProvide the 1Password API token you want to use to authenticate collection requests.modifiable
supported_apisArray of stringsYesDefine one or more of the available APIs to collect: itemUsage, and sign-in.
For example, for both you'd use: ["itemUsage","sign-in"]


1Password Source JSON example:

      "name": "1Pass",
      "base_url": "",
      "supported_apis": ["itemUsage","sign-in"],
      "api_token": "********",
      "fields": {
           "_siemForward": true


After configuring your Source, you should check the status of the source in the Collectors page > Status column. If the Source is not functioning as expected, you may see an error next to the Source Category column as shown below: 


Error Code401
Error Details{"Error":{"Message":"Unauthorized"}}

To resolve these errors:

  • Make sure the Base URL matches your domain.
  • Make sure correct API Token is used to configure the source.
  • If you're still seeing the 401 Unauthorized error in the Status column, regenerate the API Token by following these Authentication steps and then updating the API Token for the source.
Privacy Statement
Terms of Use

Copyright © 2023 by Sumo Logic, Inc.