Admin Guide

Synapse-Intel471 Admin Guide

Configuration

Synapse-Intel471 requires either an Intel471 Verity Client ID/Secret, or (for existing Titan automations) an Intel471 Titan API key. The Titan API is scheduled to be retired by Intel471 on 2026-12-31.

Getting a Verity Client ID/Secret

To obtain a Verity Client ID/Secret, visit the Intel471 Developer Portal, navigate to Applications, and select Create an Application. Once created, copy the Client ID and Client Secret values from the application details.

Setting a Verity configuration for global use

To set-up a global Verity configuration:

> intel471.verity.config.add default myclientid myclientsecret
Synapse-Intel471 Verity config "default" added

Using per-user Verity configurations

A user may set-up their own Verity configuration:

> intel471.verity.config.add --scope self myconfig myclientid myclientsecret
Synapse-Intel471 Verity config "myconfig" added

Setting a Verity tag prefix

Note: If not set, this will default to rep.intel471.

> intel471.verity.config.update default --tag-prefix my.prefix
Updated Synapse-Intel471 Verity config "default"

Setting API key for global use (Titan)

To set-up a global API key:

> intel471.setup.apikey myapiemail myapikey
WARNING: "intel471.setup.apikey" is deprecated: This command relies on the Intel471 Titan API, which Intel471 is retiring.
Setting Intel471 credentials for all users.

Using per-user API keys (Titan)

A user may set-up their own API key:

> intel471.setup.apikey --self myapiemail myapikey
WARNING: "intel471.setup.apikey" is deprecated: This command relies on the Intel471 Titan API, which Intel471 is retiring.
Setting Intel471 credentials for the current user.

Setting a tag prefix for global use (Titan)

Note: If not set, this will default to rep.intel471.

> intel471.setup.tagprefix my.prefix
WARNING: "intel471.setup.tagprefix" is deprecated: This command relies on the Intel471 Titan API, which Intel471 is retiring.
Setting Intel471 tag prefix to my.prefix.

Dependencies

Synapse-Intel471 does not have any dependencies.

Permissions

Package (synapse-intel471) defines the following permissions:
power-ups.intel471.user          : Controls user access to Synapse-Intel471. ( default: false )
power-ups.intel471.admin         : Controls administrative access to Synapse-Intel471 configuration, including proxy overrides. ( default: false )

You may add rules to users/roles directly from storm:

> auth.user.addrule visi power-ups.intel471.user
Added rule power-ups.intel471.user to user visi.

or:

> auth.role.addrule ninjas power-ups.intel471.user
Added rule power-ups.intel471.user to role ninjas.

To customize the tag prefix applied to nodes, Synapse-Intel471 requires the permission globals.set.intel471:tag:prefix to be set on the user/role. You may set this perm to users/roles directly from storm:

> auth.user.addrule visi globals.set.intel471:tag:prefix
Added rule globals.set.intel471:tag:prefix to user visi.

or:

> auth.role.addrule ninjas globals.set.intel471:tag:prefix
Added rule globals.set.intel471:tag:prefix to role ninjas.

Exported APIs

Synapse-Intel471 does not currently export any APIs.

Workflows

Synapse-Intel471 provides the following workflows in Optic:

Title: Configuration
Title: Titan Configuration (Legacy)