Exception during in-place 4.2.1 to 4.3.1 upgrade

[Max Spicer]

Thanks, both!

Incidentally, I notice that the sample metadata generated includes this
uncommented entry:

<ArtifactResolutionService
Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP" Location="
https://host.example.com:8443/idp/profile/SAML2/SOAP/ArtifactResolution"
index="2"/>

I'm surprised by the 8443 reference. However, I do appreciate that this is
only example metadata. We have `idp.artifact.enabled = false` in
idp.properties anyway.

Max

On Tue, 17 Oct 2023 at 15:30, Rod Widdowson <rdw at steadingsoftware.com>
wrote:

> > The intent was that it only runs on an initial install though, which can
> assume the usual properties. The bug might be in whatever
> > caused it to run but I seem to recall I reported that and we fixed it.
>
> In V4 it runs if it cannot file %{idp.home}\metadata\idp-metadata.xml, so
> that's another workaround - just create an empty file
> there.
>
> As Scott says its fixed and we only generate on clean installs (and even
> then only if the old file doesn't exist)
>
> Rod
>
>
> --
> For Consortium Member technical support, see
> https://shibboleth.atlassian.net/wiki/x/ZYEpPw
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20231017/9287ddfe/attachment.htm>