Windows SP 2.6.0

[Cantor, Scott]

On 6/9/17, 4:34 PM, "users on behalf of Young, Darren" <users-bounces at shibboleth.net on behalf of Darren.Young at chicagobooth.edu> wrote:

> I’d prefer to leave it so the SP does the work but I don’t think I can
> convince anyone to accept a 5 minute startup time.

Well, that would be a one-time thing for a new system in general with the flag set, I'm just saying you would need to prime it once to get it into the state it needs to be in to manage it going forward on its own. It's not formally supported to "prime" it by hand. I'm not saying it won't work (it likely will) but it isn't supported and could break if something we change breaks it.

> But that's sort of what I was thinking if this has to be disabled, have
> Puppet place the file in var/run after it installs the MSI, make the
> changes to the config XML and restart shibd_default. We would have an
> external process that downloads/validates the metadata then checks it into
> our local SVN for Puppet to distribute. I’d prefer to not do this though.

If you manage it that way, it doesn't go in var/run, it would go in etc/ as you originally asked about.

If the metadata provider is told to load from a file or path and not a url, it will look in etc/shibboleth, whereas the backingFile for a url would end up in var/cache/

You own and manage etc/ but you can't touch var/

That's Linux-oriented but the software is aligned to that convention.

I'll report back once I've had a chance to test the load time on my copy.

-- Scott