adding shibboleth-sp metadata to my idp

[Gene Matthews]

Trying to add my first real sp (testshib is working) to our idp configuration. I have added a MetadataProvider (FileSystemMetadataProvider) entry in myrelying-party.xml that points to an xml file containing the sp metadata. 

When I take my browser to their protected resource (https), I get the following in my idp-process.log. I have sent this to them to look at also. I searched (still searching) the archives of this list but haven't come up with anything that seemed to apply (or that I knew how to make use of the information). If anyone has info that will point me in the right direction I would be grateful. 

I'm wondering if it is cert related since it can't read the input, but I would think it would be a more security related error message if that was the case. 

thanks, 

gene 




08:33:56.108 - INFO [Shibboleth-Access:73] - 20130827T123356Z|76.97.170.225|carnage.hitachi-cta.com:443|/profile/SAML2/Redirect/SSO| 
08:33:56.110 - DEBUG [edu.internet2.middleware.shibboleth.idp.profile.IdPProfileHandlerManager:86] - shibboleth.HandlerManager: Looking up profile handler for request path: /SAML2/Redirect/SSO 
08:33:56.110 - DEBUG [edu.internet2.middleware.shibboleth.idp.profile.IdPProfileHandlerManager:97] - shibboleth.HandlerManager: Located profile handler of the following type for the request path: edu.internet2.middleware.shibboleth.idp.profile.saml2.SSOProfileHandler 
08:33:56.111 - DEBUG [edu.internet2.middleware.shibboleth.idp.util.HttpServletHelper:339] - LoginContext key cookie was not present in request 
08:33:56.111 - DEBUG [edu.internet2.middleware.shibboleth.idp.profile.saml2.SSOProfileHandler:188] - Incoming request does not contain a login context, processing as first leg of request 
08:33:56.112 - DEBUG [edu.internet2.middleware.shibboleth.idp.profile.saml2.SSOProfileHandler:366] - Decoding message with decoder binding 'urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect' 
08:33:56.112 - DEBUG [org.opensaml.ws.message.decoder.BaseMessageDecoder:76] - Beginning to decode message from inbound transport of type: org.opensaml.ws.transport.http.HttpServletRequestAdapter 
08:33:56.114 - DEBUG [org.opensaml.saml2.binding.decoding.HTTPRedirectDeflateDecoder:90] - Decoded RelayState: null 
08:33:56.114 - DEBUG [org.opensaml.saml2.binding.decoding.HTTPRedirectDeflateDecoder:127] - Base64 decoding and inflating SAML message 
08:33:56.117 - DEBUG [org.opensaml.ws.message.decoder.BaseMessageDecoder:183] - Parsing message stream into DOM document 
08:33:56.124 - ERROR [org.opensaml.ws.message.decoder.BaseMessageDecoder:208] - Encountered error parsing message into its DOM representation 
org.opensaml.xml.parse.XMLParserException: Unable to read XML from input stream 
... 
Caused by: java.util.zip.ZipException: invalid code lengths set 
... 
08:33:56.128 - WARN [edu.internet2.middleware.shibboleth.idp.profile.saml2.SSOProfileHandler:400] - Error decoding authentication request message 
org.opensaml.ws.message.decoder.MessageDecodingException: Encountered error parsing message into its DOM representation 
... 
Caused by: org.opensaml.xml.parse.XMLParserException: Unable to read XML from input stream 
... 
Caused by: java.util.zip.ZipException: invalid code lengths set 
... 
08:33:56.176 - DEBUG [edu.internet2.middleware.shibboleth.idp.util.HttpServletHelper:339] - LoginContext key cookie was not present in request 
08:33:56.177 - DEBUG [edu.internet2.middleware.shibboleth.idp.ui.ServiceContactTag:177] - No relying party, nothing to display 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130827/a9708338/attachment-0001.html