API Authentication, updates to the Activity Log, and Data Export Transparency
At the moment it can be unclear when users are downloading data from Domo.
For example requests against this API https://{{domo_instance}}.domo.com/api/query/v1/execute/{{dataset_id}} , do not hit the activity log; however, savy users could use this to download datasets to their computer.
I appreciate that this same query might be the query that feeds a Dataset View or a Card in Analyzer; however, when the query does not originate from the Domo UI (and instead python, postman or visual studio code), that may be a time to capture this query request in the Logs.
Similarly, if users are blind guessing at developer_token authentication (x-domo-developer-token) or using expired tokens, it would be ideal if the Activity Log surfaced that an invalid token was being used.
If an object is altered in Domo (an ETL, security settings, a certified card) it would be ideal to know how the user authorized the command - via UI or a which authentication header.
Check out my 🎥 Domo Training YouTube Channel 👨💻
**Say "Thanks" by clicking the ❤️ in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 101 SQL DataFlows
- 622 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 747 Beast Mode
- 59 App Studio
- 41 Variables
- 686 Automate
- 176 Apps
- 453 APIs & Domo Developer
- 47 Workflows
- 10 DomoAI
- 36 Predict
- 15 Jupyter Workspaces
- 21 R & Python Tiles
- 395 Distribute
- 113 Domo Everywhere
- 276 Scheduled Reports
- 6 Software Integrations
- 125 Manage
- 122 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 109 Community Announcements
- 4.8K Archive