Hi Mark,
My resilient-circuits claims that that command line parameter does not exist.
I have noticed that our resilient package is stuck at version 32. When trying to update it to v33 I get the following error:
pip install resilient -U
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
Collecting resilient
Using cached https://files.pythonhosted.org/packages/02/63/bdec37826ae09b1c6b41ce2ccb55dd677f54098b28bed1a42d76fdd4552a/resilient-33.0.189.tar.gz
Requirement already satisfied, skipping upgrade: argparse in /usr/lib/python2.7/site-packages (from resilient) (1.4.0)
Requirement already satisfied, skipping upgrade: requests>=2.6.0 in /usr/lib/python2.7/site-packages (from resilient) (2.21.0)
Requirement already satisfied, skipping upgrade: requests-toolbelt>=0.6.0 in /usr/lib/python2.7/site-packages (from resilient) (0.9.1)
Requirement already satisfied, skipping upgrade: requests-mock>=1.2.0 in /usr/lib/python2.7/site-packages (from resilient) (1.5.2)
Requirement already satisfied, skipping upgrade: six in /usr/lib/python2.7/site-packages (from resilient) (1.9.0)
Requirement already satisfied, skipping upgrade: cachetools<3.0.0 in /usr/lib/python2.7/site-packages (from resilient) (2.1.0)
Requirement already satisfied, skipping upgrade: keyring<19.0.0,>=5.4 in /usr/lib/python2.7/site-packages (from resilient) (17.1.1)
Requirement already satisfied, skipping upgrade: configparser in /usr/lib/python2.7/site-packages (from resilient) (3.7.1)
Requirement already satisfied, skipping upgrade: urllib3<1.25,>=1.21.1 in /usr/lib/python2.7/site-packages (from requests>=2.6.0->resilient) (1.24.1)
Requirement already satisfied, skipping upgrade: chardet<3.1.0,>=3.0.2 in /usr/lib/python2.7/site-packages (from requests>=2.6.0->resilient) (3.0.4)
Requirement already satisfied, skipping upgrade: idna<2.9,>=2.5 in /usr/lib/python2.7/site-packages (from requests>=2.6.0->resilient) (2.8)
Requirement already satisfied, skipping upgrade: certifi>=2017.4.17 in /usr/lib/python2.7/site-packages (from requests>=2.6.0->resilient) (2018.11.29)
Requirement already satisfied, skipping upgrade: entrypoints in /usr/lib/python2.7/site-packages (from keyring<19.0.0,>=5.4->resilient) (0.3)
Requirement already satisfied, skipping upgrade: secretstorage<3; (sys_platform == "linux2" or sys_platform == "linux") and python_version < "3.5" in /usr/lib/python2.7/site-packages (from keyring<19.0.0,>=5.4->resilient) (2.3.1)
Requirement already satisfied, skipping upgrade: cryptography in /usr/lib64/python2.7/site-packages (from secretstorage<3; (sys_platform == "linux2" or sys_platform == "linux") and python_version < "3.5"->keyring<19.0.0,>=5.4->resilient) (2.5)
Requirement already satisfied, skipping upgrade: enum34; python_version < "3" in /usr/lib/python2.7/site-packages (from cryptography->secretstorage<3; (sys_platform == "linux2" or sys_platform == "linux") and python_version < "3.5"->keyring<19.0.0,>=5.4->resilient) (1.1.6)
Requirement already satisfied, skipping upgrade: asn1crypto>=0.21.0 in /usr/lib/python2.7/site-packages (from cryptography->secretstorage<3; (sys_platform == "linux2" or sys_platform == "linux") and python_version < "3.5"->keyring<19.0.0,>=5.4->resilient) (0.24.0)
Requirement already satisfied, skipping upgrade: cffi!=1.11.3,>=1.8 in /usr/lib64/python2.7/site-packages (from cryptography->secretstorage<3; (sys_platform == "linux2" or sys_platform == "linux") and python_version < "3.5"->keyring<19.0.0,>=5.4->resilient) (1.11.5)
Requirement already satisfied, skipping upgrade: ipaddress; python_version < "3" in /usr/lib/python2.7/site-packages (from cryptography->secretstorage<3; (sys_platform == "linux2" or sys_platform == "linux") and python_version < "3.5"->keyring<19.0.0,>=5.4->resilient) (1.0.16)
Requirement already satisfied, skipping upgrade: pycparser in /usr/lib/python2.7/site-packages (from cffi!=1.11.3,>=1.8->cryptography->secretstorage<3; (sys_platform == "linux2" or sys_platform == "linux") and python_version < "3.5"->keyring<19.0.0,>=5.4->resilient) (2.19)
Installing collected packages: resilient
Found existing installation: resilient 32.0.140
Uninstalling resilient-32.0.140:
Successfully uninstalled resilient-32.0.140
Running setup.py install for resilient ... error
ERROR: Complete output from command /usr/bin/python2 -u -c 'import setuptools, tokenize;__file__='"'"'/tmp/pip-install-8RX0Qj/resilient/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-PtD2F8/install-record.txt --single-version-externally-managed --compile:
ERROR: Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/tmp/pip-install-8RX0Qj/resilient/setup.py", line 35, in <module>
check_deps()
File "/tmp/pip-install-8RX0Qj/resilient/setup.py", line 26, in check_deps
distro = get_distribution(pkg.project_name)
File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 479, in get_distribution
dist = Requirement.parse(dist)
File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3138, in parse
req, = parse_requirements(s)
File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3085, in parse_requirements
yield Requirement(line)
File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3094, in __init__
raise RequirementParseError(str(e))
pkg_resources.RequirementParseError: Invalid requirement, parse error at "'-esilien'"
----------------------------------------
Rolling back uninstall of resilient
Moving to /usr/bin/finfo
from /tmp/pip-uninstall-pL6Lzq/finfo
Moving to /usr/bin/gadget
from /tmp/pip-uninstall-pL6Lzq/gadget
Moving to /usr/bin/res-keyring
from /tmp/pip-uninstall-pL6Lzq/res-keyring
Moving to /usr/lib/python2.7/site-packages/co3
from /usr/lib/python2.7/site-packages/~o3
Moving to /usr/lib/python2.7/site-packages/resilient
from /usr/lib/python2.7/site-packages/~esilient
Moving to /usr/lib/python2.7/site-packages/resilient-32.0.140-py2.7.egg-info
from /usr/lib/python2.7/site-packages/~esilient-32.0.140-py2.7.egg-info
ERROR: Command "/usr/bin/python2 -u -c 'import setuptools, tokenize;__file__='"'"'/tmp/pip-install-8RX0Qj/resilient/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-PtD2F8/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-install-8RX0Qj/resilient/
Could this be the problem? Any idea on how to resolve the setup error?
Jerome
------------------------------
Jerome Kleinen
------------------------------
Original Message:
Sent: Tue August 20, 2019 11:47 AM
From: Mark Scherfling
Subject: Using API KEY
Jerome,
Try using --config-file with resilient-circuits run
command to reference your app.config file.
------------------------------
Mark Scherfling
Original Message:
Sent: Tue August 20, 2019 10:28 AM
From: Jerome Kleinen
Subject: Using API KEY
Hello Yongjian,
We are running resilient circuits using a systemd service file. The error we get is the following:
Aug 20 16:13:28 abcdef resilient-circuits: usage: resilient-circuits [-h] --email EMAIL [--password PASSWORD]Aug 20 16:13:28 abcdef resilient-circuits: [--host HOST] [--port PORT]Aug 20 16:13:28 abcdef resilient-circuits: [--proxy [PROXY [PROXY ...]]] [--org ORG]Aug 20 16:13:28 abcdef resilient-circuits: [--cafile CAFILE] [--cache-ttl CACHE_TTL]Aug 20 16:13:28 abcdef resilient-circuits: [--proxy_host PROXY_HOST] [--proxy_port PROXY_PORT]Aug 20 16:13:28 abcdef resilient-circuits: [--proxy_user PROXY_USER]Aug 20 16:13:28 abcdef resilient-circuits: [--proxy_password PROXY_PASSWORD]Aug 20 16:13:28 abcdef resilient-circuits: [--stomp-prefetch-limit STOMP_PREFETCH_LIMIT]Aug 20 16:13:28 abcdef resilient-circuits: [--stomp-port STOMP_PORT]Aug 20 16:13:28 abcdef resilient-circuits: [--stomp-cafile STOMP_CAFILE]Aug 20 16:13:28 abcdef resilient-circuits: [--componentsdir COMPONENTSDIR] [--noload NOLOAD]Aug 20 16:13:28 abcdef resilient-circuits: [--logdir LOGDIR] [--loglevel LOGLEVEL]Aug 20 16:13:28 abcdef resilient-circuits: [--logfile LOGFILE]Aug 20 16:13:28 abcdef resilient-circuits: [--no-prompt-password NO_PROMPT_PASSWORD]Aug 20 16:13:28 abcdef resilient-circuits: [--test-actions] [--resilient-mock RESILIENT_MOCK]Aug 20 16:13:28 abcdef resilient-circuits: [--test-host TEST_HOST] [--test-port TEST_PORT]Aug 20 16:13:28 abcdef resilient-circuits: [--log-http-responses LOG_HTTP_RESPONSES]Aug 20 16:13:28 abcdef resilient-circuits: resilient-circuits: error: argument --email is requiredAug 20 16:13:29 abcdef systemd: resilient_circuits.service: main process exited, code=exited, status=2/INVALIDARGUMENT
We have configured an API user in the Resilient UI, we have giving it all permissions and we have added it to several message destinations. In the app.config we commented out the email and password in favor of the api_key_id and api_key_secret, as per manual (Integration Server Guide, Chapter 6, Page 15).
Kr,
Jerome
------------------------------
Jerome Kleinen
Original Message:
Sent: Wed August 14, 2019 03:31 PM
From: Yongjian Feng
Subject: Using API KEY
Hello Jerome,
Could you please give us more information regarding how you used resilient-circuits? Did you create/run a function?
Thanks,
Yongjian
------------------------------
Yongjian Feng
Original Message:
Sent: Mon August 12, 2019 10:09 AM
From: Jerome Kleinen
Subject: Using API KEY
Hi Mark,
I just tried circuits v33 with an API key configured. The manual states you should configure either an API key/secret or the older email/password. When only configuring the API keys, circuits fails to start because email is supposedly a required parameter.
The manual further states that when both are configured, the API settings are used by default. However, looking at my logs, when both are configured, the regular user is chosen over the API settings.
Could you (or someone else) clarify/confirm?
Jerome
------------------------------
Jerome Kleinen
Original Message:
Sent: Fri August 02, 2019 02:20 PM
From: Mark Scherfling
Subject: Using API KEY
Resilient-circuits v33 is now published on pypi: https://pypi.org/project/resilient-circuits/. This version supports API Tokens introduced in Resilient v33.
------------------------------
Mark Scherfling
Original Message:
Sent: Thu August 01, 2019 09:10 AM
From: Mark Scherfling
Subject: Using API KEY
Hi Jasmine,
We will be publishing a new version of resilient-circuits which will support API keys very shortly. Check pypi for a version 33.0.xxx. When this is published, additional documentation will be updated on github on how to use API keys.
I'll post an update here when all that takes place.
Regards,
Mark
------------------------------
Mark Scherfling
Original Message:
Sent: Thu August 01, 2019 04:44 AM
From: Jasmine
Subject: Using API KEY
Is there any answer for this question? I really need to integrate resilient with third party apps and you don't have any document or even any answer for this issue.
------------------------------
Jasmine
Original Message:
Sent: Mon July 29, 2019 04:51 AM
From: Jasmine
Subject: Using API KEY
Hi,
Have you a proper documentation about using API KEY and API SECRET for integration resilient with external apps?
https://www.ibm.com/support/knowledgecenter/en/SSBRUQ_33.0.0/com.ibm.resilient.doc/admin/API_accounts.htm
Thanks
------------------------------
Jasmine
------------------------------