Apparently this is still happening in Jammy for some reason (maybe a regression), as according to this [1] bug report claiming that this bug is the cause of it.
This is the command that I run to hit it (doesn't need anything in particular for the command to work, can run anywhere such as a fresh new container):
Apparently this is still happening in Jammy for some reason (maybe a regression), as according to this [1] bug report claiming that this bug is the cause of it.
This is the command that I run to hit it (doesn't need anything in particular for the command to work, can run anywhere such as a fresh new container):
mellon_ create_ metadata https:/ /sp.10. 5.100.3/ mellon https:/ /sp.10. 5.100.3/ v3/OS-FEDERATIO N/identity_ providers/ idp.10. 5.100.2/ protocols/ saml2/auth/ mellon
It fails silently to create the xml file that it should be creating. It works fine in focal, but doesn't work in jammy.
Versions in jammy: mod-auth- mellon 0.18.0-1build1 openssl: amd64 1.2.33-1build2
libapache2-
apache2-bin 2.4.52-1ubuntu4.8
openssl 3.0.2-0ubuntu1.15
libssl3:amd64 3.0.2-0ubuntu1.15
libxmlsec1-
versions in focal: mod-auth- mellon 0.16.0-1ubuntu0.1 openssl: amd64 1.2.28-2
libapache2-
apache2-bin 2.4.41-4ubuntu3.16
openssl 1.1.1f-1ubuntu2.22
libssl1.1:amd64 1.1.1f-1ubuntu2.22
libxmlsec1-
[1] https:/ /bugs.launchpad .net/ubuntu/ +source/ ssl-cert/ +bug/2052795