What is the best password policy for Encryption on Workbench
We have a requirement to encrypt a few fields while uploading via workbench. What will be a good encryption password policy? Let's say we have ten fields that need to be encrypted, and 30 users need access to them that they can decrypt with a password.
- do you create 30 different encryption passwords
- how do you manage these passwords ( FOR forgotten password or periodically changing the password)
If you are encrypting your field in the workbench, please give us some pointers.
Tagged:
1
Answers
-
You can't use 30 different passwords to encrypt the data unless you have 30 different datasets which I highly recommend against as that's quite a bit of management overhead.
Typically using a password manager where you can grant or revoke access to the different accounts / passwords is good practice so you don't have passwords floating out in the wild.
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**1 -
Thanks Grant
0
Categories
- All Categories
- 1.9K Product Ideas
- 1.9K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 303 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 3K Transform
- 104 SQL DataFlows
- 640 Datasets
- 2.2K Magic ETL
- 4K Visualize
- 2.5K Charting
- 769 Beast Mode
- 72 App Studio
- 43 Variables
- 718 Automate
- 185 Apps
- 462 APIs & Domo Developer
- 57 Workflows
- 14 DomoAI
- 40 Predict
- 17 Jupyter Workspaces
- 23 R & Python Tiles
- 402 Distribute
- 116 Domo Everywhere
- 277 Scheduled Reports
- 9 Software Integrations
- 135 Manage
- 132 Governance & Security
- 8 Domo Community Gallery
- 44 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 111 Community Announcements
- 4.8K Archive