Centos IdP tomcat6 no go: shibboleth.MetadataTrustEngine error?

[Jeff Earickson]

Scott et al,

It is amazing what a good lunch will do.  I found it, I had changed

/opt/shibboleth-idp/conf/relying-party.xml

a couple of days ago in a test attempt to connect up with
testshib.org.  When I put
the original file back in place, the "curl -k
https://localhost/idp/status" started working
again, minus Apache.  Per the advice here, I'm going to leave apache
out of the picture.

Jeff Earickson
Colby College


On Wed, Sep 5, 2012 at 11:55 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 9/5/12 11:31 AM, "Jeff Earickson" <jaearick at colby.edu> wrote:
>>
>>I find the following message in /opt/shibboleth-idp/logs/idp-process.log:
>>
>>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.springframework.beans.factory.NoSuchBeanDefinitionException: No
>>bean named 'shibboleth.MetadataTrustEngine' is defined
>
> There has to be something else in the log than that, or you would have to
> have modified the configuration file in unusual ways.
>
>>1) So how did I frig this up?  What is wrong?
>
> Find the actual error and I can tell you. That's all past the point of the
> real problem.
>
>>2) How do I get a real SSL cert from Incommon installed into Tomcat IdP?
>
> The "real" cert is for browser use, it's the same as any web server. The
> Tomcat documentation covers this.
>
>>3) Should I be running Apache on this system, with the real cert in
>>/etc/pki/tls/certs?
>
> Not for any particularly reason you've given, no.
>
> -- Scott
>
>
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net