HammerDB: Passwordless MariaDB connection #408
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using SSL connection to MariaDB we are able to authenticate user solely based on SSL subject and issuer. In such a case we need to pass SSL certificate and SSL key to authenticate and we cannot pass user password, because such an user might not have an password set, which is the goal of such an configuration. Currently HammerDB always append '-password' to connection string, so we are not able to connect to MariaDB with user configured as described above. This patch adds the ability to use special keyword "null" in order to skip appending password to connection string. Such a special keyword instead of empty string was chosen in order to avoid breaking other layers of HammerDB and in order to keep the number of changes minimal.
Signed-off-by: Igor Konopko igor.j.konopko@intel.com