Fixed #14508: Added PDO::MYSQL_ATTR_SSL_VERIFY_SERVER_CERT options to database.php …

[jeffclay]

…and updated .env files to provide value for the new option.

Description

Added PDO::MYSQL_ATTR_SSL_VERIFY_SERVER_CERT options to database.php as documented here

Fixes #14508

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Tested locally

Test Configuration:

• PHP version: 8.1.27
• MySQL version 8
• Webserver version apache
• OS version Rocky Linux 9

Checklist:

• I have read the Contributing documentation available here: https://snipe-it.readme.io/docs/contributing-overview
• I have formatted this PR according to the project guidelines: https://snipe-it.readme.io/docs/contributing-overview#pull-request-guidelines
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[welcome]

💖 Thanks for this pull request! 💖

We use semantic commit messages to streamline the release process and easily generate changelogs between versions. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix if it doesn't have one already.

Examples of commit messages with semantic prefixes:

• Fixed #<issue number>: don't overwrite prevent_default if default wasn't prevented
• Added #<issue number>: add checkout functionality to assets
• Improved Asset Checkout: use new notification method for checkout

Things that will help get your PR across the finish line:

• Document any user-facing changes you've made.
• Include tests when adding/changing behavior.
• Include screenshots and animated GIFs whenever possible.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

[what-the-diff]

PR Summary

• Addition to Environment Files
  Enhancements were added in the form of new code to multiple '.env' files. These changes make sure that our application communicates securely with the database.

• Database Config File Update
  Modifications were done in our application's database configuration file. It involves the addition of certain attributes related to the verification of the SSL server. This strengthens our database connection security, providing a more secure environment for our data.

[snipe]

Should we perhaps default this to something sane if folks don't add this value to their .env?

[jeffclay]

Good point, I wasn't thinking about upgrading existing installs without updating the .env file. Let me test the behavior when the value is set to null.

[snipe]

Also check if the variable doesn't even exist in the .env :)

[welcome]

Congrats on merging your first pull request! 🎉🎉🎉