Securing the connection between Enterprise Server and Drupal can be achieved by running Drupal on HTTPS.
Step 1. This step is optional, only perform it when the following is not true:
- Enterprise Server and Drupal run on the same machine and SSL is set up for Enterprise Server
- You are happy to reuse the same certificate for Drupal
Repeat the steps from Using SSL in Enterprise Server but now for the Drupal server.
Notes:
|
Tip: You can configure Drupal on the same machine but on a different port (such as '1234'), thereby enabling you to specify a different certificate than used for Enterprise Server.
Step 2. Set up the Drupal configuration while making sure of the following:
- In the config_drupal.php file, fill in the HTTPS location of Drupal in the "url" option of the following setting:
- For Drupal 6 and 7: DRUPAL_SITES
- For Drupal 8: DRUPAL8_SITES
- Use the machine name as specified while creating the certificates:
'url' => 'https://your_server_name:443/drupal/'
Step 3. Run the Publish to Drupal test on the Heath Check page. Fix any errors where necessary.
Troubleshooting: Publish error from Drupal
When the certificate does not match, the following type of error is shown:
Drupal - Publish error from Drupal: Error in cURL request: SSL certificate problem, verify that the CA cert is OK. Details: error:1407E086:SSL routines:SSL2_SET_CERTIFICATE:certificate verify failed.
Fix this by checking the following:
- For Drupal 6 and 7: Your "local_cert" option in the DRUPAL_SITES setting of the config_drupal.php file.
- For Drupal 8: The path to the certificate.
Related Information
SSL support in WoodWing Enterprise
Related Tasks
Using SSL in Enterprise Server
Using SSL to secure the connection between Enterprise Server and Content Station
Using SSL to secure the connection between Enterprise Server and Smart Connection
Reference Materials
Comment
Do you have corrections or additional information about this article? Leave a comment! Do you have a question about what is described in this article? Please contact Support.
0 comments
Please sign in to leave a comment.