RE: SourceID.Net - SqlFederationhandler.
"Cholan NSamy" <[email protected]> Mon, 1 Sep 2003 05:54:57 -0700
| Newsgroups | gmane.comp.sourceid.sso.devel |
|---|---|
| Message-ID | <[email protected]> |
Thanks David, Now the logging out is perfect. And regarding the "located assembly's manifest definition" error, I'm using windows 2003 and also I have only one version (0.3V) of sourceID.NET in my machine. Mentalis DLL is available. Can you please suggest what to do? Cholan -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of David Waite Sent: Saturday, August 30, 2003 12:18 AM To: [email protected] Subject: Re: [SourceID SSO-dev] 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.=20 >Given below is the stacktrace for your reference. > > =20 > >Server Error in '/idp-sample' Application. >----------------------------------------------------------------------- - >-------- > >Logout request received for a NameIdentifier which does not match the >current user session=20 > =20 > <snip> >Line 412: if (uid !=3D sess[Constants.Session.UserId]) > =20 > oh wow, I am very happy you found this :-) I will reproduce this, test the fix and try to have another release out=20 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=20 defined as an Object, not a String. The in-memory federation handler=20 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. > =20 > I'm going to write a separate email about your website layout, so that=20 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.=20 >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.=20 > =20 > >Exception Details: System.IO.FileLoadException: The located assembly's >manifest definition with name 'Org.Mentalis.Security' does not match the >assembly reference. > > =20 > I believe this error is a version and public key mismatch. A previous=20 version of SourceID.NET had a version of the assembly which I compiled=20 and signed, once Mentalis started signing the package themselves this=20 was no longer necessary. Is this Windows 2003? The (newer) ASP.NET implementation is built into=20 the IIS, and I've seen several problems with this new implementation=20 pulling old assemblies from its Temporary ASP.NET Files cache directory=20 rather than using the new files. My fix has been to stop IIS and clear=20 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.)=20 > > =20 > I do not believe this is the problem, I think it is a missing or=20 older-cached Mentalis DLL. -David Waite _______________________________________________ sso-dev mailing list [email protected] http://mail.sourceid.org/mailman/listinfo/sso-dev