Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesGet current user from within a WebService ASMX fileGet current user from within a WebService ASMX file
Previous
 
Next
New Post
7/2/2015 5:40 PM
 
Since WebServices are technically accessible to the public, I want to control access to them by simply having the WebService check the current user first before doing anything else . However, I have found that WebService methods are not within the same scope as the module so using something like UserController.GetCurrentUserInfo() does not reliably return the current logged in user. I found this link which describes the issue and provides a workaround:

https://dnntracker.atlassian.net/browse/DNN-24848

All I want to know is, is there any way someone could hack the HttpContext.Current.User.Identity.Name property when trying to call a WebService (for example, change it to "host") or can I really trust that property to giving me the correct user name?

Alternatively, does anyone know a better way to verify the current user from within a WebService?
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesGet current user from within a WebService ASMX fileGet current user from within a WebService ASMX file


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out