Univention Bugzilla – Bug 44112
univention-self-service URI is in UCS 4.2 no longer available
Last modified: 2017-04-04 18:30:00 CEST
At least for the password self service sites, we need redirects from the UCS 4.1 URI (univention-self-service) to the UCS 4.2 URI (univention/self-service).
univention-self-service (2.0.13-5): r78446 | Bug #44112: add backwards compatible redirections
univention-management-console (9.0.78-1): r78462 | Bug #44112: stay backwards compatible for all URI's
It is now possible again to have a UCS 4.2 DC Master which was updated from UCS 4.1 and a UCS 4.1 DC Slave where the Self-Service frontend runs on.
All URL's like /univention-self-service/ are redirected to /univention/self-service/ with a HTTP 303 status code which preserves the #fragement and apache preserves the query-string.
OK: redirects correctly: /univention-self-service/?lang=en-US#passwordreset OK: redirects correctly: /univention-self-service/?lang=de-DE#passwordchange Links from previous token-mails don't have to be valid anymore, but links from new token mails must. REOPEN: When following the link in a sent email: ----------------------------------------------------------------------- Webfrontend error: The specified request is unknown. The path '/self-service/' was not found. ----------------------------------------------------------------------- The reason is, that the hostname of the dc master is in the email. If I replace it with the hostname of the slave (on which the App was installed) it works.
Another problem is, that univention-self-service-master is unmaintaned: root@master411:~# apt-cache policy univention-self-service-master univention-self-service-master: Installiert: (keine) Installationskandidat: 2.0.15-3A~4.2.0.201703311631 Versionstabelle: 2.0.15-3A~4.2.0.201703311631 0 500 https://updates-test.software-univention.de/4.2/unmaintained/ 4.2-0/all/ Packages root@master411:~#
(In reply to Stefan Gohmann from comment #6) > Another problem is, that univention-self-service-master is unmaintaned: Should be available after the next mirror sync. (In reply to Daniel Tröder from comment #5) > The reason is, that the hostname of the dc master is in the email. If I > replace it with the hostname of the slave (on which the App was installed) > it works. If I understand it correctly, this UCR variable is used for it: umc/self-service/passwordreset/email/webserver_address I've now added a simple listener script which checks for a server object with the registered service self-service. If the UCR variable is empty, it is set to the FQDN of the server. It is not the best solution but it should work out of the box and admins can overwrite them via UCR or via UCR policy.
(In reply to Stefan Gohmann from comment #7) > It is not the best solution but it should > work out of the box and admins can overwrite them via UCR or via UCR policy. Yes, if there is more than one system with installed and registered self service, the UCR variable might be set with one of the "other" FQDNs.
Commit is r78586 (tagged for Bug #44112). (In reply to Sönke Schwardt-Krummrich from comment #8) > (In reply to Stefan Gohmann from comment #7) > > It is not the best solution but it should > > work out of the box and admins can overwrite them via UCR or via UCR policy. > > Yes, if there is more than one system with installed and registered self > service, the UCR variable might be set with one of the "other" FQDNs. The UCRV is only set by the listener if previously unset. But it wouldn't matter anyway, as all frontends would use the same backend. The problem of varying the frontend address in the email is one that the customer can remedy by forking sending/send_email.py (optionally using the external method). The listener only triggers when a new computer object is created.
r78605: make listener trigger on change Package: univention-self-service Version: 2.0.16-3A~4.2.0.201704031100 Branch: ucs_4.2-0 Scope:
(In reply to Daniel Tröder from comment #10) > r78605: make listener trigger on change The listener will get all objects with the matching filter upon initialization anyway. I think the change is rather pointless, because the UCRv is still only set if it previously unset - but nothing breaks ;) Daniel: Please make sure that it was intended this way, and clone a specific bug for 4.2-errata if the behavior should be changed. I will set this bug to VERIFIED
UCS 4.2 has been released: https://docs.software-univention.de/release-notes-4.2-0-en.html https://docs.software-univention.de/release-notes-4.2-0-de.html If this error occurs again, please use "Clone This Bug".