Shibboleth Developers

[Nate Klingenstein <>]

Jeff,

I've encountered the same error using CentOS 5.1 and Apache 2.2.  When I did, I was under significant time pressures, and I have no access to the test environment to replicate the error now.  I guessed it had something to do with IP addresses being used for the machine's name, and moved on.  Specifically, I suspected it was an issue with the 1.0 DS implementation's handling of IP addresses causing it to return invalid parameters in the discovery response, since other session initiators still worked fine.

There might also be some mis-configuration of the server name in the virtual host; we didn't touch that, and left it default, which might've inherited a domain name that differed from what I had in the metadata.

Is there any other difference between this instance and others you're running besides the OS?  What happens if you explicitly set a ServerName and UseCanonicalName on?

Thanks,

Nate.

On 10 Apr 2008, at 00:28, <> wrote:

I am seeing a very strange failure with Shibboleth 2.0 SP on Windows 2003 Server with Apache as the web server when using a Discovery Service.  I cannot reproduce it in any other environment (switch to IIS or RHEL, and I was told by someone else seeing the same failure, it doesn’t reproduce in any of the XPs with Apache).  No error messages are logged in shibd.log or native.log. 

 

The SP redirects me to the Discovery Service, I select the  IDP, the Discovery Service redirects me back, and then Shibboleth shows this error message:

Please include the following message in any email:

shibsp::ConfigurationException at (http://winsp.ref.gfipm.net/Shibboleth.sso/DS)

Target resource was not an absolute URL.