Hide Forgot
Created attachment 1212587 [details] rhsm.log from consumer server Description of problem: Subscribing system with single custom CA configured on katello works fine but fails if there is more then one cerificate in a CA chain Version-Release number of selected component (if applicable): subscription-manager: 1.15 SAM 1.4 How reproducible: Steps to Reproduce: 1. Change certificate for katello with more then one certificate in Authority chain 2. Create an rpm with root chain certificate and consumer certificate signed by the same authority as katello certificate. 3. Install rpm on consumer server. 4. Try to subscribe, get error Unable to verify server's identity: tlsv1 alert unknown ca Actual results: System register with error and is not able to get any actions from SAM Expected results: System subscribe without any error and can use repos from SAM. Additional info: I assume that it is not a katello bug because curl and openssl s_client connects to the SAM server without any errors Please take a look at case 01713149 to see what action was taken in workaround.
Have you tried setting the 'ssl_verify_depth' to a higher value in /etc/rhsm/rhsm.conf?
Yes, i tried it - doesn't help.
I'd like a little more information from the customer on this. Specifically: 1. A tarball of the contents of /etc/rhsm on the client that is unable to subscribe successfully. 2. The openssl s_client command used to test and the entire output of the command. 3. The output of `openssl s_client -connect HOSTNAME:8443` run from the client (with an appropriate value for HOSTNAME). 4. The output of `openssl s_client -connect HOSTNAME:8443 -CAfile /etc/rhsm/ca/CA_FILE` run from the client (with appropriate values for HOSTNAME and CA_FILE).
There is a workaround involving importing the Katello server certificate into Tomcat. However, we won't officially support this. With the release of Satellite 5.8 we are deprecating the support of Subscription Asset Manager. The release notes for 5.8 can be found at https://access.redhat.com/documentation/en-us/red_hat_satellite/5.8/pdf/release_notes/Red_Hat_Satellite-5.8-Release_Notes-en-US.pdf. I am therefore closing out this bug as WONTFIX. If you believe this to be an error, please feel free tor each out to either Rich Jerrido or Bryan Kearney. Thank you!