Security for External Web services

Results 1 to 2 of 2

Thread: Security for External Web services

  1. #1
    Join Date
    Dec 1969

    Default Security for External Web services

    We have an external web service that will be invoked by our Client company. There is a dedicated T1 line with hardware encryption between us and our client company . I wanted to know what is the best way to implement security in my web service. I tried using System.Net.NetworkCredential but it needs the domain name/machine name along with user name and password. We can't expect the client to pass in the machine name as we have 6 web servers hosting the web service. Is there another way to handle web service security?

  2. #2
    Join Date
    Dec 1969

    Default few suggestions

    1) WSE 2.0 (Webservice Security Extensions i think that stands for)<BR><BR>2) On your web server hosting the Web Services, goto the IIS Website settings and only allow specific IP&#039;s to access the server

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts