 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / Languages / C# / May 2007OperationContext.Current or HttpContext.Current in MembershipProvider within WCF Service = null?
I have a custom membership provider that I am using to authenticate users in a WCF web service hosted IIS. I want to be able to see any cookies that come across and save session variables, but I cannot get to the OperationContext.Current nor the HttpContext.Current (I am using aspNetCompatibility=true and confirmed that it is enabled in the debugger) - both are null. Is there a setting someplace that will enable these to be available to the MembershipProvider? When I get into the service they are available, but not before. Is there an alternative way to get to cookie and session data in WCF? WCF deliberately divorces itself from the transport, as WCF must work equally with HTTP, TCP, MSMQ, carrier-pidgeon, etc. What specifically are you looking to do? For custom authentication, see below; for other operations, "inspectors" are often the way to go... You might also find the microsoft.public.windows.developer.winfx.indigo group more apt. http://groups.google.co.uk/group/microsoft.public.windows.developer.winfx.indigo /browse_thread/thread/5b4d8a5790e76feb/4040905d321cce17 Marc > microsoft.public.windows.developer.winfx.indigo group Oops! my bad... my aggregator confused me... I thought this was somewhere else ;-p Marc (ahh... multipost... don't do that ;-p) > WCF deliberately divorces itself from the transport, as WCF must work > equally with HTTP, TCP, MSMQ, carrier-pidgeon, etc. [quoted text clipped - 9 lines] > > Marc I need to pass in a third-party session id, along with the username and password that is used for authentication for a WCF service that is hosted in IIS. I was hoping to use a cookie to return the session id to the client and have them resubmit it on each request. I am using a custom membership provider to implement the custom authentication logic. I use this membership provider for web apps also so it has to be ASP.NET compatible. When I use the attribute to make WCF ASP.NET compatible I see neither the HttpContext nor the OperationContext.Current objects. These appear to not be instantiated until I get past the authentication process in WCF - in plain asp.net this works fine. Can anyone confirm that this is normal behavior for WCF? Also, is there a way that cookie data gets mapped to objects in WCF? Lastly, other than using custom tokens or explicit parameters, are there any other recommended approaches to passing in data to be used in the preprocessing of a WCF service request? Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.