Usually db tests run using a *test* user whose credentials are shared anyway so this doesnt matter in most cases. The bottom line is if JMeter can get the password , so can a user (no matter what form of encryption you use) - The only way out would be to have the user specify the password when he runs the test(as suggested by sebb using properties) ...
regards deepak On Fri, Jul 9, 2010 at 12:56 PM, black gaff <[email protected]>wrote: > > I've created a script that does Oracle SQL requests, using the JDBC > Connection Configuration config element. > > In the config element are fields for UserName and Password. The Password > field is not masked, so if I share this file with anyone on my team, they > can see my password. > > Is there a way to mask this password, similar to the way passwords are > masked using HTTP Authorization Manager? > > I know I could pass the login credentials in with a CSV file, but I was > hoping for something more contained. Is there a way to access the value of > a > Password stored in HTTP Authorization Manager by referencing it's variable > name? If so, how? > > Much thanks, Joe > > -- > View this message in context: > http://jmeter.512774.n5.nabble.com/Any-way-to-mask-JDBC-login-credentials-tp1045689p1045689.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
