Hello,
Recently after reviewing MyEclipse with our DBAs, they were concerned that it:
1. Gives the user the option of saving the database password
2. Stores that password in clear text
Short-term we’d like it if MyEclipse could provide us with a version of sqlexplorer that either doesn’t have the save password option, or is just broken where it doesn’t write the proper or any value in the password area of the stored connections.
Long-term, or if you can provide quickly even as a pilot to us, we might be able to live with a solution where the password was hashed, but there are some DBAs in our company that might still prefer the ability to only hand out the tool without save password as an option.
Obviously you need a solution that is maintainable as a single development stream for MyEclipse though. I’m sure that others would want password encryption and perhaps there could be a hidden preference that we (or other enterprise MyEclipse clients) could hard code ourselves into the preference file regarding not completing the save portion of a password so that we could achieve our limitation of the product, but all normal users wouldn’t see this. Let me know what might be possible,
Jay