Unable to connect Azure Paas DB with SSL Enabled

ragunathankmindsprint commented 9 months ago

Preconditions and environment

Magento version : 2.4.5-p1 - Magento community edition
Added the below config in app/etc/env.php file for connecting Azure Paas Database with SSL Enabled and getting the below error.

Config : 'db' => [ 'table_prefix' => '', 'connection' => [ 'default' => [ 'host' => 'xxxxxxxxxxxxxxx', 'dbname' => 'xxxxxx', 'username' => 'xxxxxxx', 'password' => 'xxxxxxxx', 'model' => 'mysql4', 'engine' => 'innodb', 'initStatements' => 'SET NAMES utf8;', 'active' => '1', 'driver_options' => [ 1014 => true ] ] ] ],

Error : SQLSTATE[HY000] [9002] SSL connection is required. Please specify SSL options and retry.

SSL Enabled Screenshot :

Steps to reproduce

Example :

Open env.php file
Enable SSL in Azure Pass DB

Added the below code in app/etc/env.php file in db section.

'db' => [
    'table_prefix' => '',
    'connection' => [
        'default' => [
            'host' => 'xxxxxxxxxxxxxxx',
            'dbname' => 'xxxxxx',
            'username' => 'xxxxxxx',
            'password' => 'xxxxxxxx',
            'model' => 'mysql4',
            'engine' => 'innodb',
            'initStatements' => 'SET NAMES utf8;',
            'active' => '1',
            'driver_options' => [
                1014 => true
            ]
        ]
    ]
],

Run the setup upgrade command : php bin/magento setup:upgrade;

Expected result

Upgrade successful.

Actual result

Error : SQLSTATE[HY000] [9002] SSL connection is required. Please specify SSL options and retry.

Azure DB Enabled :

Additional information

No response

Release note

No response

Triage and priority

[X] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
[ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
[ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
[ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
[ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

m2-assistant[bot] commented 9 months ago

Hi @olamragunathank. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release
For more details, review the Magento Contributor Assistant documentation.
Add a comment to assign the issue: @magento I am working on this
To learn more about issue processing workflow, refer to the Code Contributions.

Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

srsathish92 commented 9 months ago

@olamragunathank I think you have to add an SSL certificate in the env.php

'driver_options' => [
        1014 => true,
        1009 => '/path to certificate/CA.crt.pem'
    ]

m2-assistant[bot] commented 9 months ago

Hi @engcom-Dash. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
1. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
1. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
1. Verify that the issue is reproducible on 2.4-develop branch
  Details
  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

Join Magento Community Engineering Slack and ask your questions in #github channel.

souzapsl commented 8 months ago

@magento give me 2.4.5-p1 instance

magento-deployment-service[bot] commented 8 months ago

Hi @souzapsl. Thank you for your request. I'm working on Magento instance for you.

magento-deployment-service[bot] commented 8 months ago

Hi @souzapsl, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

souzapsl commented 8 months ago

@magento give me 2.4.6-p2 instance

magento-deployment-service[bot] commented 8 months ago

Hi @souzapsl. Thank you for your request. I'm working on Magento instance for you.

magento-deployment-service[bot] commented 8 months ago

Hi @souzapsl, unfortunately there is no ability to deploy Magento instance at the moment. Please try again later.

engcom-Hotel commented 4 months ago

We are moving this issue On hold as we are discussing this issue with the PO.

Thanks

magento / magento2