<!-H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}->
</style>
</head>
<body>
h1. HTTP Status 404 - Servlet !IdP is not available
<HR size="1" noshade="noshade">
type Status report
message
<u>
Servlet IdP is not available
</u>
description
<u>
The requested resource (Servlet IdP is not available) is not available.
</u>
<HR size="1" noshade="noshade">
h3. Apache Tomcat/5..
There are a variety of 404 errors that may be thrown in response to one of the multiple web mechanisms involved in a Shibboleth transaction, but this particular 404 is frequently encountered. The above error is displayed by Tomcat when it is unable to load the IdP servlet for some reason. Most frequently, the idp.xml file or the MetaData will be misconfigured. Check the catalina.out Tomcat log file for more details, and consult IdP Common Errors for further ideas.