Storing Secrets for Scripts: Difference between revisions

From QPR ProcessAnalyzer Wiki
Jump to navigation Jump to search
No edit summary
Line 15: Line 15:
The secure strings can be used in the following places:
The secure strings can be used in the following places:
* [[QPR ProcessAnalyzer Scripting Commands|SQL scripting commands]]: ImportOdbcQuery, ImportOleDbQuery, ImportSalesforceQuery, ImportSapQuery and ImportSqlQuery.
* [[QPR ProcessAnalyzer Scripting Commands|SQL scripting commands]]: ImportOdbcQuery, ImportOleDbQuery, ImportSalesforceQuery, ImportSapQuery and ImportSqlQuery.
* In the [[QPR_ProcessAnalyzer_Model_Datasources#Loading_Data_from_ODBC_Datasource|models' ODBC datasources].
* In the [[QPR_ProcessAnalyzer_Model_Datasources#Loading_Data_from_ODBC_Datasource|models' ODBC datasources]].
* In the [[Generic_Properties_and_Functions_in_QPR_ProcessAnalyzer_Expressions#ImportOdbcSecure|ImportODBCSecure function]] in the expression language
* In the [[Generic_Properties_and_Functions_in_QPR_ProcessAnalyzer_Expressions#ImportOdbcSecure|ImportODBCSecure function]] in the expression language

Revision as of 18:43, 15 March 2020

The secure strings provide a way to store passwords an other confidential information to QPR ProcessAnalyzer in a way that the information can be used, but no user can see the information in plaintext. For example, in ETL scripts SAP, Salesforce and ODBC passwords can be stored as secure strings, which can then be referred in the ETL script commands.

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

Storing Secure Strings

Odbc = 1 Sap = 2 Salesforce = 3 Sql = 4 OleDb = 5

Using Secure String

The secure strings can be used in the following places: