shibboleth2.4 configuration error

jfu jfu_gengyue at hotmail.com
Thu Nov 21 17:44:49 EST 2013


Thank you.


Our sys admin reconfigure the Tomcat/Apache. Since this is just test server,
we are using http. 

I also undeploy idp.war, and then I rerun install.sh.

When asked the qualified hostname of idp, I input test.mycompany.com and
keystore is automatically generated.

Then, I followed the instruction to create a context descriptor to deploy
idp.war. XML libraries used by IDP has been endorsed. I restart tomcat
server

I browse http://test.mycompany.com/idp/Authn/UserPassword. The example login
shows.
I browse http://test.mycompany.com/idp/shibboleth, and it brings up xml
file. I still see entityID is https://test.mycompany.com

  <?xml version="1.0" encoding="UTF-8" ?> 
+ <EntityDescriptor xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
entityID="https://test.mycompany.com/idp/shibboleth"
xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
xmlns:shibmd="urn:mace:shibboleth:metadata:1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

I am not sure if this is correct or not. I continue to configure shibboleth

1. Add metadataProvider:

  <metadata:MetadataProvider id="TranzlogicMD"
xsi:type="metadata:FileBackedHTTPMetadataProvider"
                         
metadataURL="http://SP_IPAddress/simplesamlphp/www/module.php/saml/sp/metadata.php/default-sp"
                         backingFile="/opt/shibboleth-idp/metadata/sp.xml" >
            <metadata:MetadataFilter xsi:type="metadata:ChainingFilter">
                <metadata:MetadataFilter
xsi:type="metadata:RequiredValidUntil"
                                maxValidityInterval="P7D" />
                <metadata:MetadataFilter
xsi:type="metadata:SignatureValidation"
                               
trustEngineRef="shibboleth.SPMetadataTrustEngine"
                                requireSignedMetadata="true" />
            </metadata:MetadataFilter>
        </metadata:MetadataProvider>

2. Security Configuration: saml.pem and saml.crt are given by our SP
<security:TrustEngine id="shibboleth.SPMetadataTrustEngine"
xsi:type="security:StaticPKIXSignature">

       <security:ValidationInfo id="SPCredentials"
xsi:type="security:PKIXFilesystem">
             
<security:Certificate>/opt/shibboleth-idp/credentials/saml.pem</security:Certificate>
       </security:ValidationInfo>
    </security:TrustEngine>

3. restart tomcat
4. idp cannot be started and error shown in idp-process.log

16:39:16.011 - ERROR
[edu.internet2.middleware.shibboleth.common.config.BaseService:188] -
Configuration was not loaded for shibboleth.RelyingPartyConfigurationManager
service, error creating components.  The root cause of this error was:
org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was
found starting with element 'metadata:MetadataProvider'. One of
'{"urn:mace:shibboleth:2.0:security":Credential,
"urn:mace:shibboleth:2.0:security":TrustEngine,
"urn:mace:shibboleth:2.0:security":SecurityPolicy}' is expected.

Please help. Thank you.




--
View this message in context: http://shibboleth.1660669.n2.nabble.com/shibboleth2-4-configuration-error-tp7591617p7591651.html
Sent from the Shibboleth - Users mailing list archive at Nabble.com.


More information about the users mailing list