Storing Secrets for Scripts

Secrets provide a way to store passwords and other confidential data in QPR ProcessAnalyzer, so that it can be used without users seeing the original plaintext. For example in ETL scripts, SAP, Salesforce and ODBC passwords can be stored as secrets, which can be referred by their names in the ETL script commands.

When the secure strings are stored, the purpose (called type of the secure string) of the secure string is also defined. Following types are available: Odbc connection strings, SAP passwords and Salesforce passwords. For example, if a secure string type is SAP password, it cannot be used as an ODBC connection string.

Secure strings are project specific, so their permissions come from the project. To use a secure string, the user needs to have at least GenericRead permission to the project.

Note: Currently ImportSqlQuery and ImportOleDbQuery don't yet support defining password as a secure string.

Setting secrets

Secrets can be set using SetSecret function for Project entities. There is also Secrets property for project entities to list all secrets in the project.

Using secrets

Secrets can be used in the following commands:

• SQL scripting commands: ImportOdbcQuery, ImportSalesforceQuery and ImportSapQuery.
• ODBC datasources of model.
• ImportODBCSecure function (expression language)