Back to bug 47700

Who When What Removed Added
heidelberger 2018-08-30 14:43:45 CEST User Pain 0.069
Who will be affected by this bug? --- 1: Will affect a very few installed domains
Summary Configure SAML Single Sign-On as single server solution doesn't work with Lets' Encrypt cert "Configure SAML Single Sign-On as single server solution" doesn't work with Let's Encrypt cert
How will those affected feel about the bug? --- 3: A User would likely not purchase the product
What type of bug is this? --- 4: Minor Usability: Impairs usability in secondary scenarios
What kind of report is it? --- Bug Report
damrose 2018-09-03 09:42:39 CEST CC damrose
michelsmidt 2018-09-03 21:40:19 CEST CC smidt
heidelberger 2018-09-04 10:38:00 CEST Status NEW RESOLVED
Resolution --- INVALID
requate 2018-09-06 20:38:10 CEST CC requate
Assignee ucs-maintainers heidelberger
QA Contact ucs-maintainers brodersen
brodersen 2018-10-22 18:54:37 CEST Status RESOLVED REOPENED
CC brodersen, scheinig
Resolution INVALID ---
scheinig 2018-10-23 09:21:49 CEST User Pain 0.069 0.137
Ticket number 2018101521000551
Who will be affected by this bug? 1: Will affect a very few installed domains 2: Will only affect a few installed domains
School Customer affected? Yes
requate 2018-11-05 10:48:48 CET Assignee heidelberger ahlers
scheinig 2018-11-06 11:18:36 CET Waiting Support Yes
brodersen 2018-11-06 17:26:18 CET Assignee ahlers brodersen
QA Contact brodersen ahlers
damrose 2018-11-07 16:45:35 CET Summary "Configure SAML Single Sign-On as single server solution" doesn't work with Let's Encrypt cert SAML Single Sign-On issues with Let's Encrypt cert
brodersen 2018-11-13 11:36:37 CET Status REOPENED RESOLVED
Resolution --- FIXED
ahlers 2018-11-15 15:52:23 CET Status RESOLVED VERIFIED
damrose 2018-11-20 09:31:15 CET Target Milestone --- UCS 4.3-2-errata
requate 2018-12-05 14:39:15 CET Status VERIFIED CLOSED
best 2019-03-17 16:07:50 CET CC best
gulden 2020-02-14 10:41:28 CET CC gulden
best 2022-04-21 15:15:33 CEST See Also https://forge.univention.org/bugzilla/show_bug.cgi?id=54567

Back to bug 47700