<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN'>
<html><head><meta http-equiv="Content-Type" content="text/html;charset=us-ascii">
<style>BODY{font:10pt Tahoma,Verdana,sans-serif} .MsoNormal{line-height:120%;margin:0}</style></head><body>
<br><blockquote style="padding-left: 5px; margin-left: 5px; border-left: #0000ff 2px solid; margin-right: 0px"><br>
> <mailto:<a href="mailto:a.thermil@crous-amiens.fr">a.thermil@crous-amiens.fr</a>>> wrote:<br>
> ><br>
> >It gives the error for some SP.<br>
><br>
> I don't see how that's possible. Even if you take SAML 1 support out<br>
> of a<br>
> particular relying party definition, I don't think it gives that<br>
> error, I<br>
> think it says something about a profile not being configured for<br>
> that RP.<br>
> But I guess you can check that.<br>
><br>
> Otherwise there'd have to be something wrong with the request URL coming<br>
> in from that SP. Perhaps it looks like it's /Shibboleth/SSO but really<br>
> isn't in some subtle way.<br>
><br>
> -- Scott<br>
><br>
> Do you mean that these SP can't support my configuration, or their<br>
> configurations<br>
> are not very good?<br>
<br>
<br>
Just to hazard a guess:<br>
<br>
Perhaps your IdP's metadata was corrupted/reencoded when you provided it <br>
to the SP, so that the SSO endpoint URLs got corrupted?<br>
<br><span></span></blockquote><div id="kerio-curpos"> I don't think so. If it was like that, it would not run for other SP. It works for some SP.</div><div id="kerio-curpos">But for other one it has that error.</div><div id="kerio-curpos">I think maybe their metadata files is not synchronized with mine. I will try that way.</div><div id="kerio-curpos"><br></div><div id="kerio-curpos">Thank you very much guys. </div><blockquote style="padding-left: 5px; margin-left: 5px; border-left: #0000ff 2px solid; margin-right: 0px"><span></span><br>
</blockquote><style>
</style>
</body></html>