Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DuoLogSync: Shutting down due to [telephony producer: [Received 401 Invalid integration key in request credentials]] #14

Open
szahri opened this issue Oct 29, 2020 · 1 comment

Comments

@szahri
Copy link

szahri commented Oct 29, 2020

Hi there,
In DUO admin I created an application called DuoSyncLog with type "Auth API" and used the integration key and secret key shown in the config.yml.
However when I started duo sync log I received the following error:

2020-10-30 00:12:37 INFO     Starting DuoLogSync
2020-10-30 00:12:37 INFO     DuoLogSync: Opening connection to mysyslogserver:514
2020-10-30 00:12:37 INFO     duo_client Admin initialized for ikey: DIIR45GSRB91OIDAA58C, host: api-12345.duosecurity.com
2020-10-30 00:12:37 INFO     telephony producer: fetching next logs after 120 seconds
2020-10-30 00:12:37 INFO     telephony consumer: waiting for logs

2020-10-30 00:14:37 INFO     telephony producer: fetching logs
2020-10-30 00:14:38 ERROR    DuoLogSync: check that the duoclient ikey and skey in the config file are correct
2020-10-30 00:14:38 WARNING  DuoLogSync: Shutting down due to [telephony producer: [Received 401 Invalid integration key in request credentials]]
2020-10-30 00:14:38 INFO     telephony producer: shutting down
2020-10-30 00:14:38 INFO     telephony consumer: shutting down

What could I be doing wrong? Am I using the wrong application type here in DUO?

appreciate any feedback!

Thanks J

@rohanbendre
Copy link

Hi @szahri! This error usually indicates you might be using incorrect integration key. I see in your description you used Auth API. You should be using Admin API and grant appropriate permissions within it.

coltwill pushed a commit that referenced this issue Nov 6, 2024
* Code changes to retry the failed request on http 429

* Changed the retry logic to try until succeed

* Improved error message

* Change severity from error to warning

* Dropped duplicate logging

* fix: ensure log_offset is properly printing instead of None in log

* chore: bump version to 2.2.3

* Logging improvements for DLS - 1

* Logging improvements for DLS - 2

* Rollback version number

* Fixed the failing test case

* Updated the change log.

* Fixed the code duplication due to mc res

---------

Co-authored-by: Sudharsan-VS <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants