Bug 46818 - Check if Certificates are Properly Copied
Check if Certificates are Properly Copied
Status: REOPENED
Product: UCS
Classification: Unclassified
Component: UMC - System diagnostic
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-04-13 08:08 CEST by Christian Völker
Modified: 2020-07-29 16:28 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2018040421000903, 2020072721000566
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Völker univentionstaff 2018-04-13 08:08:11 CEST
During the renewal process for certificates the official SDB#37 states:
---------------------------------
The following command can be used to make the newly created certificate available to all users via the UCS master’s central administration website

cp ucsCA/CAcert.pem /var/www/ucs-root-ca.crt

---------------------------------

To copy the certificate to /var/www is a very important steps and not just optional. If the old certificate remain in /var/www it is not possible to install UCS@school on a newly installed and joined UCS-Server.

The ucs@school install script will produce an ssl-error if tried.

Reason is the install script assumes it is not joined yet and downloads the above certificate through apache to verify further communication. But if the certificate under /var/www is not valid any furthe communication stops.
Comment 1 Christian Völker univentionstaff 2018-04-13 08:09:28 CEST
The system diagnostic should check if the certificate in /var/www is identical to the ones at /etc
Comment 2 Ingo Steuwer univentionstaff 2020-07-03 20:51:54 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.
Comment 3 Christian Völker univentionstaff 2020-07-29 16:28:02 CEST
Reopen because happens again for a customer and took a lot of time until I cam to the root cause.


This time the CA certificates on the backup where different. Master was fine.

But due to DNS-Round-Robin the backup was asked which caused an issue.