Forum Discussion

SmartWolf's avatar
SmartWolf
New Contributor
6 years ago

Encrypted properties are being displayed in Jenkins logs when test fails

We have Ready API tests integrated with our Jenkins builds using the Jenkins plugin. We are running into an issue with encryption of sensitive information in the Ready API tests. We have certain fi...
  • groovyguy's avatar
    groovyguy
    6 years ago

    For me, I had to set the property that was sensitive with data and then override it with a Jenkins parameter and with an overloaded property in the project itself. In my case, I was using a WSS-Config password, so I set a pair of Project-level properties, certPath and certPass. Since certPass was sensitive, that was set up as a global jenkins password, and my testrunner script looked like this:

     

     

    exit_status=$(testrunner.sh "-FXML" "-RJUnit-Style HTML Report" -J -a -A -r "-PcertPath=${certPath}" "-PcertPass=${certPass}" ${WORKSPACE}/path/to/project.xml
nmrao's avatar
nmrao
Champion Level 3
Would it be possible to explain the issue with sample log to understand the issue better? Need not be exact data.
What sort of properties are those? Any password or so?
groovyguy's avatar
groovyguy
Community Hero
6 years ago

I ran into a similar problem with passwords/sensitive information, at least when it came to being output in the Jenkins console. I was able to obfuscate that by setting it as a global level password property within Jenkins and referencing it as a paramter. I believe that made Jenkins obfuscate, in this instance, the password. 

For the reports, you might have to augment the reporting logic to override that. I want to say I've seen similar posts here in the forums on that. 

  • SmartWolf's avatar
    SmartWolf
    New Contributor
    6 years ago

    How do you refernce the global Jenkins property within the Ready API project?

    • groovyguy's avatar
      groovyguy
      Community Hero
      6 years ago

      For me, I had to set the property that was sensitive with data and then override it with a Jenkins parameter and with an overloaded property in the project itself. In my case, I was using a WSS-Config password, so I set a pair of Project-level properties, certPath and certPass. Since certPass was sensitive, that was set up as a global jenkins password, and my testrunner script looked like this:

       

       

      exit_status=$(testrunner.sh "-FXML" "-RJUnit-Style HTML Report" -J -a -A -r "-PcertPath=${certPath}" "-PcertPass=${certPass}" ${WORKSPACE}/path/to/project.xml
      • Olga_T's avatar
        Olga_T
        SmartBear Alumni (Retired)
        6 years ago

        Hi all,

         

        Thank you for sharing your knowledge, groovyguy!

         

        SmartWolf, if this information was useful, could you please click the Accept as Solution button below the reply that helped you?
        Thank you in advance!

Recent Discussions