Bug 39899 - Certificate renewal: Two logins required to complete process
Certificate renewal: Two logins required to complete process
Product: UCS
Classification: Unclassified
Component: UMC - Certificate settings
UCS 4.1
Other Linux
: P5 normal (vote)
: UCS 4.1-x
Assigned To: UMC maintainers
Depends on:
  Show dependency treegraph
Reported: 2015-11-12 11:32 CET by Erik Damrose
Modified: 2019-01-03 07:18 CET (History)
2 users (show)

See Also:
What kind of report is it?: ---
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?:
ISV affected?:
Waiting Support:
Ticket number:
Bug group (optional): Usability
Max CVSS v3 score:


Note You need to log in before you can comment on or make changes to this bug.
Description Erik Damrose univentionstaff 2015-11-12 11:32:45 CET
When updating the certificate via the UMC module, one gets logged out during the certificate creation, as UMC- and UMC-Web-server are restarted (can be seen in setup.log). After logging back in, a popup is shown that reads:

Die Änderungen wurden erfolgreich übernommen.
Bitte bestätigen Sie den Neustart der UMC-Server-Komponenten und des HTTP-Web-Servers. Dies wird ungefähr 10 Sekunden dauern.
Hinweis: Nach dem Neustart werden Sie zur Login-Seite weitergeleitet werden.

Only if 'restart' is clicked in this dialog the apache webserver will be restarted and the new certificate will become activated.

=> One has to login two times to complete the process.
Comment 1 Florian Best univentionstaff 2015-11-12 11:40:47 CET
Side effect of Bug #39476.
Comment 2 Stefan Gohmann univentionstaff 2019-01-03 07:18:14 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.