SP v3 prerelease (windows)

Doan, Tommy tdoan at smu.edu
Mon Jul 9 20:42:01 EDT 2018


Probably functionally minor but environment variable SHIBSP_PREFIX should be set to C:\opt\shibboleth-sp rather than C:/opt/shibboleth-sp.

One other comment. This tripped me up for quite a while until I did a file compare to the dist version of shibboleth2.xml and then noticed the documentation. 
https://wiki.shibboleth.net/confluence/display/SP3/FolderMetadataProvider 

        <MetadataProvider type="XML" validate="true" path="idp-metadata.xml"/>

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. 

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

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

On 7/9/18, 7:57 PM, "dev on behalf of Doan, Tommy" <dev-bounces at shibboleth.net on behalf of tdoan at smu.edu> wrote:

> I just went through the Remove procedure again and confirmed the modules are not removed from IIS.

On my test VM they definitely are, so that basically leaves it at "Windows is broken, news at 11."

You should still be able to use the appcmd.exe approach to "unregister" the module, I would think, there shouldn't be any need to manually do it (in the sense of using the GUI). Actually, if it doesn't, that basically *is* the problem, since that's what the installer actually does at uninstall. It can't make that work if the commands just refuse to do what they're supposed to, it doesn't directly touch the config.

-- Scott


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


More information about the dev mailing list