Abbreviations, used in manual:
QG - Quality Gates
In QG module, in the left side menu go to "Settings -> Data Sources -> NoSQL":
A list of all existing Data Sources will be displayed on the main screen, you can edit an existing Data Source(s) or click "Add Data Source" button to create a new Data Source:
Name - Data Source name.
Type - the following two types are available for choice:
1. Cassandra - the following fields will be available:
Host - IP address or hostname for connection server.
SSL - enable if you are using SSL.
Port - relevant port number.
Keyspace - relevant key space value. Allows the connection to focus on a specific collection of tables and configuration settings within Cassandra
Filter by - allows to specify criteria for filtering the tables within the key space based on certain values.
Test Connection button - validates that the connection works properly and returns the correct number of collections.
Assigned Projects - the Data Source must be assigned to relevant Project(s). When assigned, a Data Source will appear in the Data Sources list in the Project's Data Set(s).
2. MongoDB - the following fields will be available:
Host - IP address or hostname for connection server.
SSL - enable it if you are using SSL. The following fields will be available:
Trust store path - the file path to the trust store, which is a repository containing trusted certificates from external sources. It allows the client to verify the identity of the server. If contains a value => "Trust store type" field will be required:
Trust store password - the password required to access the trust store file. This protects the trust store and prevents unauthorized access to the certificates.
Trust store type - the format of the trust store, commonly JKS (Java KeyStore), PKCS12, or other types. This specifies how the trust store file is structured and should match the format of the actual file.
Key store path - the file path to the key store, which holds private keys and certificates for the client. This is used if mutual SSL (client authentication) is enabled, where both the client and server verify each other’s identity.
Key store password - the password to access the key store file. This ensures that only authorized applications can access and use the client’s private keys and certificates.
Key store type - the format of the key store, similar to the trust store type, such as JKS or PKCS12. This specifies how the key store file is structured and should be compatible with the file format.
Port - relevant port number.
Authorization - choose the appropriate authentication type from the list:
Default - built-in authentication type if no specific mechanism is set.
GSSAPI - Kerberos-based authentication.
MONGODB-CR - original MongoDB authentication method.
x.509 - uses X.509 certificates for client authentication.
PLAIN - LDAP authentication, sends credentials as plain text.
SCRAM-SHA-1 - Salted Challenge Response Authentication Mechanism using SHA-1 hashing.
SCRAM-SHA-256 - Salted Challenge Response Authentication Mechanism using SHA-256 hashing.
Selecting an authentication type will display a "Username" field, for MongoDB user credentials used for authentication.
For Authorization types Default, MONGODB-CR, PLAIN and SCRAM-SHA-1/256, a "Password" field will also appear.
For Authorization types Default and SCRAM-SHA-1/256, a "Database Name for Authentication" field will be shown, specifying the database MongoDB uses to verify credentials.
Database name - relevant DB name that will be used for the connection.
Filter by - filter will narrow down the tables list within the connection. Application client is limited to get a list of tables under the connection up to 500. If your connection accedes to that number of tables, you should use the filter and create a designated connection (e.g. by schema or prefix).
Comments
0 comments
Article is closed for comments.