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
StreamAlert currently has a Duo application for pulling logs from the legacy v1 logs API.
Description
This should be updated to use the newer v2 API which has more query options, which we probably don't care about, and gives much more information, which we do care about.
Update to use this API. In particular, the problem this solves is having the user IDs in the logs and not just the usernames. Usernames can change, which makes it hard to track changes over time. The user IDs do not change. The other additional information provided by this API is also useful.
The text was updated successfully, but these errors were encountered:
since the schema of returned data changes, this should probably be done as a separate app into a separate table, so one can choose to run both for a period as queries are migrated. for example, the username field was a string, but it gets replaced with a user dict which contains the user_id and username,.
Background
StreamAlert currently has a Duo application for pulling logs from the legacy v1 logs API.
Description
This should be updated to use the newer v2 API which has more query options, which we probably don't care about, and gives much more information, which we do care about.
Steps to Reproduce
Use the Duo app.
Desired Change
https://duo.com/docs/adminapi#authentication-logs
Update to use this API. In particular, the problem this solves is having the user IDs in the logs and not just the usernames. Usernames can change, which makes it hard to track changes over time. The user IDs do not change. The other additional information provided by this API is also useful.
The text was updated successfully, but these errors were encountered: