XML validation problem in apache when upgrading SP from v2 to v3

[Simon McLeish]

Hi Scott,

That's precisely what I did - there were no warnings remaining when I
changed the namespace declarations apart from the general "DEPRECATED:
legacy 2.0 configuration, support will be removed from a future version of
the software". Even in the 1,853 log lines when the XML Tooling log level
is turned up to debug, there is nothing there. And I get the same lack of
any warning if I restart shibd with the declarations changed to 3.0 - it's
apache which isn't happy. And mod_shib in apache doesn't log anything when
reloaded with the declarations set at 2.0.

Cheers,
Simon



On Thu, Jan 3, 2019 at 2:18 PM Cantor, Scott <cantor.2 at osu.edu> wrote:

> > The initial few lines of the shibboleth2.xml file with the XML
> declarations are:
>
> That's a 2.0 configuration namespace, so that has to be consistent
> throughout the file. If it's bumped to 3.0 then there are certain old
> settings that break but either way it's got to be consistent across the
> file.
>
> Per the docs, run in 2.0 mode, check for warnings, fix them, then bump the
> namespace.
>
> -- Scott
>
> --
> For Consortium Member technical support, see
> https://wiki.shibboleth.net/confluence/x/coFAAg
> 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/20190103/7a484ddb/attachment.html>