As per security consideration in our organization we have a constraints to use permitted certificates generated via certificate Authority signature from certificate authority process. As per our security standards it is mandate for us to have certificates with keyUsage=critical
As per the documentation it is mentioned that "The certificate/keystore used to sign the jar file (during the jarsigner step) cannot have the combination of KeyUsage = critical and ExtendedKeyUsage = serverAuth. The combination is not allowed to sign code."
Question: How can we configure the Secure communication for Release Operation Center (ROC) UI and ASAP studio aligned to our security policy?
The consideration for enabling SSL with respect to various component of CA Release Automation (CA RA) is mentioned below:
CA RA: 6.5, 6.6 and higher
Note: It may also be applicable for the lower release versions. However the document is validated with most recent version of RA
Secure Communication CA Release Automation: https://docops.ca.com/ca-release-automation/6-6/en/installation/ca-release-automation-security/secure-communications