Need to encrypt databricks.Token in the the pojo job definition
search cancel

Need to encrypt databricks.Token in the the pojo job definition

book

Article ID: 385821

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

Need a way to add the databricks.Token in the pojo job definition so the token string is not flat text and viewable in the the job definition

Environment

AutoSys 12.1.x and above

Agent 12.1.x and above

Resolution

There are 3 different options for specifying an encrypted password for your databrick pojo job.

1) One option would to be use a global variable

NOTE: A global variable is limited to 100 characters

You will use the Agent password utility to get the encrypted password. You can use either the DES option or the AES option. The default option is DES. After generating the encrypted password, you can put it into a global variable. Then add it to the J2EE parameters as:

String=$$myglobalvar

Again, if the encrypted password is longer than 100 characters, it will not work

2) A second option would be to use a security profile

You can create a security profile by choosing option 8 in autosys_secure

After creating a security profile, you can go to the Job Editor in WCC and do the following:

- In the Job Editor choose the HTTP job type

- Click on one of the {$} and it will bring up a Generate expression window

- In the Security Profile field, start typing your security profile and it will bring

  up a list of security profiles

- Choose your security profile that you created earlier

- Click in the key name field and select your token

- It will populate your expression in the Generated expression field

- Copy your expression and put it in the job definition under the J2EE parameters

Here is an example:

String=$$sec_profile^sa@databricks@<k>token</k>

3) A third option would be to use the embedded token in the job definition

You can run the Agent password utility to encrypt the password

You can use either DES or AES. The default is DES

An AES encrypted password is more secure

Under the J2EE parameters of your job definition, you would put your token

Here is an example:

databricks.Token=<results from running the Agent password utility>