Page History
...
| Field | Description | Example |
|---|---|---|
| sp_con_name | Lowercased connection name, used as salt | repository |
| sp_con_string | ODBC Connection String | dsn=$DSN$;uid=$USER$;pwd=$PASSWORD$; |
| sp_user_name | User Name | redscheduler_user |
| sp_encrypted_pwd | Encrypted Password | VTj0Q2xapJEWpQed8DJYvBEEnRedR94NstiHJUlLt0gC |
authConfig | Auth Configuration JSON | {} |
| token_1 | Encrypted Token | VTj0Q2xapJEWpQed8DJYvBEEnRedR94NstiHJUlLt0gC |
| token_2 | Encrypted Token | VTj0Q2xapJEWpQed8DJYvBEEnRedR94NstiHJUlLt0gC |
| token_3 | Encrypted Token | VTj0Q2xapJEWpQed8DJYvBEEnRedR94NstiHJUlLt0gC |
Encryption
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.local.properties file of each Azkaban server instance. The password values in both the Azkaban properties files and the Azkaban Users.xml file can also be stored using encryption so that they do not appear in plain text in those files. See Azkaban properties for more details.
...