Ownership of API Clients


Hello,
We have a user that has left the company and they have created numerous Client APIs that are being used in integrations throughout our company. How can I transfer ownership of those clients so we do not need to reissue new clients and update all integrations using them.
Thank you.
Chris
Best Answer
-
Changing ownership of the API Clients isn't possible as this isn't a security best practice. Due to your former user having access to these codes they would technically still have access to them and could potentially still access your platform. I'd highly recommend cycling out these credentials and creating new ones. Yes it's more work and more difficult but good security isn't always easy.
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**1
Answers
-
@Chris_Wolman Assuming the previous user was using dataset connectors, you should be able to add additional owners to the dataset account:
0 -
@MichelleH these are API Clients and not dataset accounts. I already transferred ownership of the dataset accounts. The API Clients are created through developer.domo.com and you can delete them from the Admin screen but you cannot assign new owners. I checked the CLI Tool and it does not appear that you can use the swap-owner command on API Clients.
Chris
0 -
I played around with the API and tried to find a way to change the owner. As far as I can tell, it is not possible. The best thing you can do is probably just create a new one and replace everywhere the old one is used, as sucky as that is.
Was this comment helpful? Click Agree or Like below.
Did this comment solve your problem? Accept it as the solution!1 -
Changing ownership of the API Clients isn't possible as this isn't a security best practice. Due to your former user having access to these codes they would technically still have access to them and could potentially still access your platform. I'd highly recommend cycling out these credentials and creating new ones. Yes it's more work and more difficult but good security isn't always easy.
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**1
Categories
- All Categories
- 1.9K Product Ideas
- 1.9K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 305 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 3K Transform
- 107 SQL DataFlows
- 648 Datasets
- 2.2K Magic ETL
- 4K Visualize
- 2.5K Charting
- 775 Beast Mode
- 75 App Studio
- 43 Variables
- 734 Automate
- 186 Apps
- 471 APIs & Domo Developer
- 63 Workflows
- 14 DomoAI
- 40 Predict
- 17 Jupyter Workspaces
- 23 R & Python Tiles
- 403 Distribute
- 117 Domo Everywhere
- 277 Scheduled Reports
- 9 Software Integrations
- 137 Manage
- 134 Governance & Security
- 8 Domo Community Gallery
- 44 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 113 Community Announcements
- 4.8K Archive