SP v3 prerelease (windows)

[Doan, Tommy]

I'm testing with a fresh v3 installation, but my shibboleth2.xml was largely built from an existing v2 file where the file attribute of the MetadataProvider element is used, so this isn't coming from any documentation I've seen - at least not for many years. By the way, nothing is logged in any SP log when this causes a crash, but the following Event ID 1000 does appear in the Event Viewer's Application log although not very helpful. 

Faulting application name: shibd.exe, version: 3.0.0.0, time stamp: 0x5b400ce7
Faulting module name: xmltooling3_0.dll, version: 3.0.0.0, time stamp: 0x5b4007d4
Exception code: 0xc0000005
Fault offset: 0x00042667
Faulting process id: 0x1010
Faulting application start time: 0x01d417e3efc6f310
Faulting application path: C:\opt\shibboleth-sp\sbin\shibd.exe
Faulting module path: C:\Program Files (x86)\Shibboleth\SP\lib\xmltooling3_0.dll
Report Id: c201d960-e372-45c8-b07d-8b64c3333f0b
Faulting package full name: 
Faulting package-relative application ID:

-----Original Message-----
From: dev <dev-bounces at shibboleth.net> On Behalf Of Cantor, Scott
Sent: Monday, July 9, 2018 7:58 PM
To: Shib Dev <dev at shibboleth.net>
Subject: Re: SP v3 prerelease (windows)

On 7/9/18, 8:52 PM, "dev on behalf of Cantor, Scott" <dev-bounces at shibboleth.net on behalf of cantor.2 at osu.edu> wrote:

> > Versus the v2 'file' attribute which is now a breaking configuration 
> > that prevents the service from starting or shibd - check from running. It would be helpful if possible for an error to be returned at least pointing to shibboleth2.xml.

I misread you, the Folder reference confused me.

If you use this:

        <MetadataProvider type="XML" file="idp-metadata.xml"/>

That works fine in an upgraded system, and there will a DEPRECATED warning in the log telling you exactly what it found and what to do with it. And if you bump the namespace without fixing it first, yes, it breaks (and it should say why there also). If you see any DEPRECATEDs in the log, you are going to break it if you just change the namespace, with the exception of the warnings that are actually noting it's using the old namespace.

The deprecation warnings are, by and large, extremely specific.

-- Scott


--
To unsubscribe from this list send an email to dev-unsubscribe at shibboleth.net