This paragraph didn't work for us. It instructs to create a symlink to the leaf certificate and that made our new Satellite instance still NOT trust the LDAP server (AD domain controller). What DID work was to run the same command but pointing it to the root certificate of the CA chain that signed the LDAP leaft certificate, and which was in the same folder indicated above. Then it worked immediately. Reported by: eeas_lsa https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html/installing_satellite_server_in_a_connected_network_environment/configuring_external_authentication_satellite#annotations:6803b6e7-dd1a-4e7a-885b-5e5df8b48ea4
Hello, Many thanks for using the Direct Documentation Feedback tool to report this suggestion for improvement. The BZ will go through proper team triage and info about related documentation updates will be shared in this ticket. Thank you!
Dear User, The /tmp/example.crt mentioned in the document is just for the purpose of reference. You need to change the name of the certificate as per the cert file you received. Can you please elaborate on what exact commands were executed? Thank you.
Dear User, We haven't received any response from you regarding the issue you are facing while following the procedure from the Satellite Documentation. However, we have cleared the query on the same in our last comment and we are sure it will work for you. We are closing this ticket due to inactivity. Feel free to re-open it in case you find any insightful information. Thank you for your feedback on the Satellite Documentation.