You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
INFO:cartography.sync:Starting sync stage 'gcp'
DEBUG:cartography.intel.gcp:Error occurred calling GoogleCredentials.get_application_default().
Traceback (most recent call last):
File "/home/ec2-user/.local/lib/python3.7/site-packages/cartography/intel/gcp/__init__.py", line 128, in start_gcp_ingestion
credentials = GoogleCredentials.get_application_default()
File "/home/ec2-user/.local/lib/python3.7/site-packages/oauth2client/client.py", line 1271, in get_application_default
return GoogleCredentials._get_implicit_credentials()
File "/home/ec2-user/.local/lib/python3.7/site-packages/oauth2client/client.py", line 1261, in _get_implicit_credentials
raise ApplicationDefaultCredentialsError(ADC_HELP_MSG)
oauth2client.client.ApplicationDefaultCredentialsError: The Application Default Credentials are not available. They are available if running in Google Compute Engine. Otherwise, the environment variable GOOGLE_APPLICATION_CREDENTIALS must be defined pointing to a file defining the credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
ERROR:cartography.intel.gcp:Unable to initialize Google Compute Platform creds. If you don't have GCP data or don't want to load GCP data then you can ignore this message. Otherwise, the error code is: The Application Default Credentials are not available. They are available if running in Google Compute Engine. Otherwise, the environment variable GOOGLE_APPLICATION_CREDENTIALS must be defined pointing to a file defining the credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information. Make sure your GCP credentials are configured correctly, your credentials file (if any) is valid, and that the identity you are authenticating to has the securityReviewer role attached.
INFO:cartography.sync:Finishing sync stage 'gcp'
INFO:cartography.sync:Starting sync stage 'gsuite'
DEBUG:cartography.intel.gsuite:Error occurred calling GoogleCredentials.get_application_default().
Traceback (most recent call last):
File "/home/ec2-user/.local/lib/python3.7/site-packages/cartography/intel/gsuite/__init__.py", line 61, in start_gsuite_ingestion
credentials = GoogleCredentials.from_stream(GSUITE_CREDS)
File "/home/ec2-user/.local/lib/python3.7/site-packages/oauth2client/client.py", line 1299, in from_stream
'The parameter passed to the from_stream() '
oauth2client.client.ApplicationDefaultCredentialsError: The parameter passed to the from_stream() method should point to a file.
ERROR:cartography.intel.gsuite:Unable to initialize GSuite creds. If you don't have GSuite data or don't want to load Gsuite data then you can ignore this message. Otherwise, the error code is: The parameter passed to the from_stream() method should point to a file. Make sure your GSuite credentials are configured correctly, your credentials file (if any) is valid. For more details see README
INFO:cartography.sync:Finishing sync stage 'gsuite'
INFO:cartography.sync:Starting sync stage 'crxcavator'
WARNING:cartography.intel.crxcavator:CRXcavator import is not configured - skipping this module. See docs to configure.
INFO:cartography.sync:Finishing sync stage 'crxcavator'
INFO:cartography.sync:Starting sync stage 'okta'
ERROR:cartography.sync:Unhandled exception during sync stage 'okta'
Traceback (most recent call last):
File "/home/ec2-user/.local/lib/python3.7/site-packages/cartography/sync.py", line 69, in run
stage_func(neo4j_session, config)
File "/home/ec2-user/.local/lib/python3.7/site-packages/cartography/intel/okta/__init__.py", line 37, in start_okta_ingestion
if not config.okta_api_key:
AttributeError: 'Namespace' object has no attribute 'okta_api_key'
The text was updated successfully, but these errors were encountered:
kmcquade
added a commit
to kmcquade/cartography
that referenced
this issue
Dec 22, 2019
Still getting this error, even after #204 and the most recent release (0.13.1). Same issue was present in #202
I fixed it so that it works for me. I will submit a PR.
@achantavy FYI.
The text was updated successfully, but these errors were encountered: