I have a scenario where I want to use webservices to populate data on the client side so I can really speed up the AJAX process.  I don't want to use UpdatePanels because they have too much overhead with the v13wstat3 and stuff (a 29kb+ request/response vs 1-2kb).  I have the webservice working just fine with exception of one thing: security.

Now, I know I could use IWeb for this but I can't seem to find anything in IWeb about accessing the CURRENTLY logged in user in DNN.  Everything in the IWeb project talks about doing it from a separate client altogether, whether another web client or windows client, etc. 

What I'm trying to do is through the ScriptManager -- I've added a reference in there to my webservice so it can autogenerate the JS proxies, then I can easily access them from my javascript code for that page.

So currently I have a SomeService.asmx in my module folder and I access it using the MS ScriptManager.

Anybody have any ideas how I can make the service aware of the currently logged in user, that'd be great.  Using DotNetNuke.Entities.Users.UserController.GetCurrentUserInfo does not work in this context. 

If anybody has a way to make it work with IWeb, I'd gladly switch over.

As a "workaround" I know I can just slap an object into session and then make the webmethod enable session, pull that object back out, and work with it.  That isn't exactly the most secure way of going about this.  That would also render it useless from an external program standpoint but I'm just fine with that because I only *want* it to work from the DNN app.

Thanks in advance.

Actually here is a JavaScript example that might be easier:

http://dnnsilverlight.adefwebserver.com/Silverlight10/SilverlightXAML/tabid/56/Default.aspx

Michael,

As always, your help is absolutely invaluable.  Thank you very much for that sample... I've looked at that code and sample (silverlight) before but it never stuck out to me about the authentication part.  Ingenious way of passing the credentials along in the webservice call and making sure it is dynamic enough that somebody couldn't just fake the call after sniffing the packet. 

Your tutorials and posts are by far some of the most helpful out there and when I was first getting started with module development are what got me going.  Since then I've developed around 18 fully featured modules for internal consumption at my place of employment, two commercial modules, and one free module (and many more in my "planned development" list).

Thanks a ton, you rock!