DM Actions in CDA fail with error 500 when IIS set to https

book

Article ID: 221552

calendar_today

Updated On:

Products

CA Continuous Delivery Automation - Automation Engine

Issue/Introduction

When disabling http in the IIS, some actions from DM Action Pack such as ExecuteApplicationWorkflow fail to connect to the CDA with Status 500.

Some others, such as CreateDeployPackage work fine with the same setup.

Temporarily activating http (port 80) on CDAs IIS and trying the ExecuteApplicationWorkflow Action again using the non-ssl Endpoint is working fine.

Cause

Documentation bug, missing DeploymentService configuration for supporting https only in web.config

Environment

Release : 12.2 and 12.3

Component : Continuous Delivery Automation (CDA or ARA)

Sub-Component: Release Manager (versions 9.x and 10.x)

Resolution

The following needs to be changed to enable https only for deploymentservice in web.config as well as the other changes described in documentation:

- change binding="mexHttpBinding" for DeploymentService and IntegrationService to binding="mexHttpsBinding"
- Remove or comment out "DeploymentServiceBindingNoSec" binding and endpoints using it.

Example:

...
<serviceMetadata httpGetEnabled="false" httpsGetEnabled="true" />
...
<endpoint address="mex" binding="mexHttpsBinding" contract ="IMetadataExchange" />
...

Then restart the IIS Application to take into account the changes.

This information will be available in the official documentation and the skeleton of web.config will include these sections in future versions.

Additional Information

Attached two examples of web.config for versions 9.x and 10.x of Release Manager

Attachments

1628762553830__web.config_v10 get_app
1628762541315__web.config_v9 get_app