No MetadataProvider available

[Nate Klingenstein]

The message is unambiguous: metadata download failed, couldn't connect.  The bits that you identified could certainly cause that failure if it's not the right configuration for your particular network configuration.

I'd try removing the TransportOption and seeing what happens -- anything's better than getting an orange gryphon of death(we love deployers who update their error pages ;D ).  If it still fails to connect, "it's a network issue", and you'll need to know the right magic words to whisper to your network to get through the gate.

On Jun 5, 2013, at 14:18 , John Westwood wrote:

Would I be right in thinking the problem is something to do with TransportOption? I don't know why we are using a HTTP proxy, the address is for accessing the University's Intranet from an external location. Maybe I could try commenting out this line and restarted Shibboleth / Apache?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130605/76e5af57/attachment.html