Re: SourceID.Net - SqlFederationhandler.

Cholan NSamy wrote:

>Hi David,
>
>Thanks very much for your reply David. I'm able to understand the
>process. I still have some doubts, but before that, regarding logout
>error. Yes I always face this problem while logging out. 
>Given below is the stacktrace for your reference.
>
>  
>
>Server Error in '/idp-sample' Application.
>------------------------------------------------------------------------
>--------
>
>Logout request received for a NameIdentifier which does not match the
>current user session 
>  
>
<snip>

>Line 412:            if (uid != sess[Constants.Session.UserId])
>  
>
oh wow, I am very happy you found this :-)

I will reproduce this, test the fix and try to have another release out 
Monday, but in the meantime, you might try changing this line to

Line 412:            if (!uid.Equals(sess[Constants.Session.UserId]))

Operator overloading is not a shortcut for Equals() in C#, and uid is 
defined as an Object, not a String. The in-memory federation handler 
saves the original strings, so it is comparing the reference again.

>And regarding my doubt, let's say my website acts as a service provider.
>  
>
I'm going to write a separate email about your website layout, so that 
the subjects stay separate.

>3. I tried to create another application apart from sp-sample and
>idp-sample. It just throws an error given below.
>
>The located assembly's manifest definition with name
>'Org.Mentalis.Security' does not match the assembly reference. 
>Description: An unhandled exception occurred during the execution of the
>current web request. Please review the stack trace for more information
>about the error and where it originated in the code. 
>  
>
>Exception Details: System.IO.FileLoadException: The located assembly's
>manifest definition with name 'Org.Mentalis.Security' does not match the
>assembly reference.
>
>  
>
I believe this error is a version and public key mismatch. A previous 
version of SourceID.NET had a version of the assembly which I compiled 
and signed, once Mentalis started signing the package themselves this 
was no longer necessary.

Is this Windows 2003? The (newer) ASP.NET implementation is built into 
the IIS, and I've seen several problems with this new implementation 
pulling old assemblies from its Temporary ASP.NET Files cache directory 
rather than using the new files. My fix has been to stop IIS and clear 
out this directory.

>I'm able to guess that is due to invalid certification ( in the sense
>that copied the same web.config file used in sp-sample, but the paths
>were to change to point the corresponding application both in web.config
>as well as provider.xml files.) 
>
>  
>
I do not believe this is the problem, I think it is a missing or 
older-cached Mentalis DLL.

-David Waite