<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I went back and took the original login page, added the graphics
from our web team and made the changes to referencing the campus
resource; what I also changed was to reference the login.css prior
to the campus style sheet (they created their own for headers and
footers), and removed reference in the css and in the login.jsp to
their unique table structure. Lo and behold the install script
compiled and the IDP is now operational. So - I can't tell you
exactly if it was the style sheet order or if it was an issue with
overtly custom table references for the login fields. (while still
using required elements). Either way it as Chad stated below I
believe; tomcat did not like what was loading into memory prior to
completion and seemed to reject the entire element. <br>
<br>
Thanks to all those who responded.<br>
<br>
--------------------------------------------------------<br>
<pre wrap="">Date: Mon, 19 Mar 2012 17:57:34 -0400
Chad La Joie <a class="moz-txt-link-rfc2396E" href="mailto:lajoie@itumi.biz"><lajoie@itumi.biz></a>
Subject: Re: changes in login pages - kills IDP?
To: Shib Users <a class="moz-txt-link-rfc2396E" href="mailto:users@shibboleth.net"><users@shibboleth.net></a>
Message-ID:
<a class="moz-txt-link-rfc2396E" href="mailto:CACTY7uBFUtDGS1ikYZ_==XXPWALxfB6_L5yPjxJP=FfeQi4ezg@mail.gmail.com"><CACTY7uBFUtDGS1ikYZ_==XXPWALxfB6_L5yPjxJP=FfeQi4ezg@mail.gmail.com></a>
Content-Type: text/plain; charset=ISO-8859-1
The behavior your describing is uncommon for JSP changes. Those are
compiled at runtime when a request comes in and if the compilation
fails Tomcat spits out some gross stacktrace.
So I'd do what Paul just suggested and then log in to the Tomcat
manager and see what it says the status of the IdP app and what
context path it claims to be mounted under. I'm wondering if the
web.xml file is corrupted in some way. Did you add anything to it
(e.g., servlet filters or taglibs) when doing the JSP updates? If
taglibs, perhaps a TLDs is corrupted to. Whatever it is, it's
something Tomcat is checking <b class="moz-txt-star"><span class="moz-txt-tag">*</span>before<span class="moz-txt-tag">*</span></b> it starts up anything to do with
the IdP itself.
On Mon, Mar 19, 2012 at 17:35, Oleg Chaikovsky
<a class="moz-txt-link-rfc2396E" href="mailto:oleg.chaikovsky@aegisusa.net"><oleg.chaikovsky@aegisusa.net></a> wrote:
</pre>
<blockquote type="cite" style="color: #000000;">
<pre wrap="">
Yeah - I pretty much felt this was the issue but the catalina.out log
file did not offer succinct clues to me (well, at least that pointed me
in the right direction). the threads errors were well known in this list
that its something that can be ignored. it also showed the deployment
descriptor for idp.xml which made me wonder why that showed up.
I realize this is the shib list, and not the tomcat list. If you can
point me to a possible avenue
of solution I will go there otherwise I will check Tomcat lists
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Oleg Chaikovsky
AegisUSA - The Identity Company
303-222-1064
714-742-2823 mobile
<a class="moz-txt-link-freetext" href="http://www.aegisusa.com">http://www.aegisusa.com</a>
twitter- @aegisidentity</pre>
</body>
</html>