Hey Ewan,

The reason you're not getting a proper user id is because the code executing in your web method doesn't have any of the handy "current context" you'd normally have during a request. If you look at the source for that method you're calling, you'll see the first thing it does is check the current http context.

A quick fix for this would be to modify your web method to accept a user id or user name parameter and pass it in from the client side.

you could add something like this in your ascx

<script type="text/javascript">

var currentUserId = <% GetCurrentUserInfo.UserID %>;

</script>

And then when you make your ajax call, just use that JS variable.

Hope that helps,

Ian

This was the first thread, that I encountered when I googled out for this issue. I was doing it just for academic purposes. So, for those people who read this thread, I would like to mention that although Ian's approach works, IMHO it is not advisable to be followed at all. This opens the door to impersonation attempts where-in someone can try to pass userid manually using Http sniffers like fiddler, adn cause a whole lot of security concerns.

Although I use custom code for the resolution of this, IWeb in my opinion provides a comprehensive solution to the problem. If in hurry, you can use the other suggested approach for Identity, but I would rather never pass plain UserId/Username etc. fro js to a web-service.