> I assume that this is a problem with my SAML1 configuration since they're > both using the Shibboleth.SSO bean (and they're the only SPs that I have that > use this particular bean) It's not. I can't imagine what could cause that error, let alone be isolated to one profile. There's a system failure or corruption of some kind involved. -- Scott