Hi Joris,

Hope you’re doing well :)

I’m not sure if you configured the credentials in Jenkins correctly and whether you are including them correctly in the script. So let’s dubbel check!

And to be clear, the actual LifeTime authorization token (secret) should not be included in the script. 

If the LT token is configured correctly as a credential in Jenkins, it will be fetched by use of the credential ID which by the default is the string ‘LifeTimeServiceAccountToken’.

Now, in the Python script file make sure you have the AuthorizationToken variable set correctly with the value (mind the single quotes): 

credentials(‘LifeTimeServiceAccountToken’) 

In this case LifeTimeServiceAccountToken is the credentials ID used in Jenkins.

Let me know how it goes!

Regards,

Nordin

Ha Nordin!

Thanks for the quick reaction. Nice that we can work on this together :-D. 

Yes, I stored the Lifetimetoken in the Manage Jenkins | Manage Credentials configuration part of Jenkins. That is the place I safely can store the token. 

But Groovy detects I am using the token in a an insecure way. 

Warning: A secret was passed to "powershell" using Groovy String interpolation, which is insecure.
         Affected argument(s) used the following variable(s): [AuthorizationToken]

For now, as a workaround, I hardcoded the token in the Jeninks script. But that is even more insecure I am afraid.

Hi Dorus,

The string interpolation warning is caused by the way in which you refer to the credential variable on each python script call.

For more info on how string interpolation works, please check here: https://docs.cloudbees.com/docs/admin-resources/latest/automating-with-jenkinsfile/string-interpolation

Regards,
Duarte

Thanks Duarte, 

You described it is a warning  (and not an error). So I tried again, and it is working now. Maybe also due to installation of new plugins.

Kind regards,

Joris