<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
On 4/18/12 4:23 PM, Karla Borecky wrote:
<blockquote
cite="mid:CADSzqNKxMrSaophtzXgv3BXB24diANE8VhxSokzSZSxdmJUy=A@mail.gmail.com"
type="cite">The only step I didn't do yet was to modify the idp
metadata file to add an SSO endpoint. I don't know if that's a
deal-breaker? Perhaps so. Goodness knows the error could be in any
one of those files! I just started with the first one it
complained about. </blockquote>
<br>
<br>
If you are still dealing with the "Classpath resource does not
exist" error: no, that wouldn't have anything to do with, nor would
any of the other config files. That cause of that error is
unambiguously that you aren't running the idp.war that you think you
are.<br>
<br>
<br>
<br>
<blockquote
cite="mid:CADSzqNKxMrSaophtzXgv3BXB24diANE8VhxSokzSZSxdmJUy=A@mail.gmail.com"
type="cite">I sort of figure the internal.xml file must be loaded
early on in the process, though.</blockquote>
<br>
<br>
It is. It is in fact the first one loaded. See the idp.war's
/WEB-INF/web.xml. None of this is relevant to your problem though.<br>
<br>
<br>
<blockquote
cite="mid:CADSzqNKxMrSaophtzXgv3BXB24diANE8VhxSokzSZSxdmJUy=A@mail.gmail.com"
type="cite">
<div>
<br>
</div>
<div>I'm attaching the whole shebang. I feel confident the idp.war
that shows the correct contents is in the right place (<span
style="font-family:'Times New Roman'"><span
style="font-family:Arial;vertical-align:baseline;white-space:pre-wrap">/srv/tomcat6/webapps
- running SLES 11 SP1, FYI.)</span></span></div>
<div><font face="Arial"><span style="white-space:pre-wrap"><br>
</span></font></div>
</blockquote>
<br>
Well, that is a hint as to the idp.war problem. We usually don't
recommend that you copy or put the war in the webapps directory
because, amongst other reasons, Tomcat does seemingly unpredictable
things with what it actually deploys, especially if you have it set
to unpack the war. We recommend that you use a context deployment
fragment, as documented here:<br>
<br>
<br>
<a class="moz-txt-link-freetext" href="https://wiki.shibboleth.net/confluence/display/SHIB2/IdPApacheTomcatPrepare">https://wiki.shibboleth.net/confluence/display/SHIB2/IdPApacheTomcatPrepare</a><br>
<br>
That section in the wiki even highlights the exact issue you are
probably experiencing.<br>
<br>
--Brent<br>
<br>
<br>
<br>
</body>
</html>