What is the best password policy for Encryption on Workbench
Options
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.5K Product Ideas
- 1.5K Ideas Exchange
- 1.4K Connect
- 1.1K Connectors
- 283 Workbench
- 4 Cloud Amplifier
- 4 Federated
- 2.7K Transform
- 90 SQL DataFlows
- 565 Datasets
- 2K Magic ETL
- 3.4K Visualize
- 2.3K Charting
- 592 Beast Mode
- 13 App Studio
- 28 Variables
- 588 Automate
- 143 Apps
- 417 APIs & Domo Developer
- 27 Workflows
- 1 DomoAI
- 28 Predict
- 12 Jupyter Workspaces
- 16 R & Python Tiles
- 361 Distribute
- 99 Domo Everywhere
- 260 Scheduled Reports
- 2 Software Integrations
- 95 Manage
- 92 Governance & Security
- 15 Product Releases
- Community Forums
- 37 Getting Started
- 28 Community Member Introductions
- 90 Community Announcements
- 4.8K Archive