☑ cool new feature
☐ could help many users!
☑ removes a „bug“ [~ lack of security]
☐ nice to have
☐ nobody needs it
What inspired this wish list request?
If the Database driver doesn't allow the user to store the password in the ODBC settings, it is difficult to store database passwords in a secure and simple way.
Very insecure: store the database password as plain text in the JSL and table (!!!) script
With Jmp17 ,there is the new option to Hide ODBC Connection String which leads to the effect that
Another option:
Encrypt the code for the database connection:
JMP-and-Oracle-Tips-and-Tricks-for-a-Happy-Marriage
But then it is essential to use a Run Password. Otherwise, everybody with access to the code has access to the data base.
And the run password just shifts the problem - and makes it more difficult to automate it.
The best approach:
Store the Password at a save location and give Jmp access to the password:
Unfortunately, this approach is not compatible with Query Builder.
What is the improvement you would like to see?
Include a credential manager / connection to Windows credential manager in the Query Builder to automatically store database passwords in a secure, well-defined and simple way.
e.g. along the idea of @ih
Please add a functionality to Create Database Connection() and New SQL Query( Connection()) such that they can use the stored passwords as well.
Why is this idea important?
A secure, well-defined and simple way to manage credentials - this is where standardization can help a lot.
The best: directly include it into the existing Query Builder ecosystem.
2 Comments