Integrating with a Service 🧩

nexploit-cli integration [options] connects NeuraLegion with ticketing and management services deployed on local servers (currently only the On-Premise Jira is supported). The repositories of the connected services can then be integrated with the NeuraLegion projects and used as endpoints for the scan reports.

For more information about the integration capabilities, see Ticketing Systems.

Script Example

nexploit-cli integration --access-key INTEGRATION_ACCESS_KEY --base-url https://acme.atlassian.net --user username --password pa$$word --token API_TOKEN 

Options

Option Description
--cluster NeuraLegion cluster (domain name).

Default:https://app.neuralegion.com
--access-key=integrationKey The unique identifier generated on the JIRA INTEGRATION CONFIG popup in the NeuraLegion App.
Required to authorize NeuraLegion to the On-Premise Jira (local Jira Server).
--type=jira Integration service type (currently only JIRA is supported).
--base-url=serviceUrl The base URL to the Jira instance API.
--user=serviceUserName Use a username for a local Jira Server or email for the Atlassian Jira Cloud.
--password=serviceUserPassword Use a password for a local Jira Server or API token for the Atlassian Jira Cloud.
--token=apiKey,
-t=apiKey
Nexploit organization API key or personal API key with the bot scope.
The botscope enables connection between Nexploit and the Nexploit CLI.
--daemon,
-d
Runs the integration in a daemon mode.
--config=pathToConfig Specifies the path to the configuration file. By default, the CLI tries to discover the config in package.json in the root directory of your application or a separate file by a specified name in the working directory. For details, see Configuration Files for more information.
--log-level
=0/1/2/3/4/silent/
error/warn/notice/verbose
Allows setting the level of logs to report. Any logs of a higher level than the one specified are shown. The options to select : 0, 1, 2, 3, 4, "silent", "error", "warn", "notice", "verbose".

Default: 3
--insecure Allows the Nexploit CLI to proceed and operate even if the server connection is considered insecure.
--proxy=socksProxyUrl SOCKS URL to proxy all traffic.

Note: SOCKS4, SOCKS5, SOCKS4a, SOCKS5h are currently supported. By default, if you specify SOCKS://<URL> , then SOCKS5h is applied.
--bus=eventBusUrl (Deprecated). NeuraLegion event bus URL.

Default:--bus amqps://amq.app.neuralegion.com:5672

Did this page help you?