in simple terms you attach a soap header to the service and verify the information within the service.
You would still require SSL if you're concerned about packet sniffing.
Of course your within a windows domain. Maybe you could configure the virtual directory where the services are stored to reject anomomous requests and required Windows Integrated Authentication.
then from within the webservice you could authenticate the current user with the current identity [tt]System.Security.Principal.WindowsIdentity.GetCurrent();[/tt]. This way you don't need to worry about the soap header.
Yea, I am looking for something specific to SQL reporting services. I need to know what functions can be used to check a user's permissions before presenting them with an option to edit report properties.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.