Page History
...
WhereScape provides an encryption utility as a stand-alone tool as well as being imbedded in the applicable Azkaban components. Azkaban decryption of WhereScape encrypted passwords expects the salt used for encryption to be the lowercased connection name. Azkaban has access to the Profile Password, required for decryption, via a new property (com.wherescape.red.profilePassword) in the azkaban.loclalocal.properties file of each Azkaban server instance. The password values in both the Azkaban properties files and the Azkaban Users.xml file are can also be stored using encryption so that they do not appear in plain text in those files. See Azkaban properties for more details.
See encryption-util.jar section for more details on using the WhereScape encryption utility.
...
Next the script attempts to update the "redamin"."ws_scheduler_profile" with the Profile details provided and outputs the result and the insert statement to the results pane of RED.
| Info |
|---|
| This script will need to be run every time you add a new connection to RED, so that the Scheduler Profile is kept in-sync. The subsequent times you run this script the UI will be prepopulated with any existing records in the "redamin"."ws_scheduler_profile" so that you do not have to re-enter them but allows updating any records as required. |