Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Web Development
  3. ASP.NET
  4. Making sure that only MYapplication can using MY webservice?

Making sure that only MYapplication can using MY webservice?

Scheduled Pinned Locked Moved ASP.NET
question
9 Posts 5 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C Offline
    C Offline
    Cormac M Redmond
    wrote on last edited by
    #1

    Hi. I have a webservice - and I want to make sure that only MY application is using it. Is this possible, in a secure way? Thanks, Cormac

    T M 2 Replies Last reply
    0
    • C Cormac M Redmond

      Hi. I have a webservice - and I want to make sure that only MY application is using it. Is this possible, in a secure way? Thanks, Cormac

      T Offline
      T Offline
      Tarakeshwar Reddy
      wrote on last edited by
      #2

      Have a look at WebService Authentication[^] & Authentication for webservices[^] on code project

      C 1 Reply Last reply
      0
      • T Tarakeshwar Reddy

        Have a look at WebService Authentication[^] & Authentication for webservices[^] on code project

        C Offline
        C Offline
        Cormac M Redmond
        wrote on last edited by
        #3

        Thanks. Unfortunately, those techniques rely on username and password credentials. I need to prevent my users from being able to build their own applications andthen using my web service with their username and password. Regards, Cormac

        T C 2 Replies Last reply
        0
        • C Cormac M Redmond

          Thanks. Unfortunately, those techniques rely on username and password credentials. I need to prevent my users from being able to build their own applications andthen using my web service with their username and password. Regards, Cormac

          T Offline
          T Offline
          Tarakeshwar Reddy
          wrote on last edited by
          #4

          Instead of using the username and password of the users, you can have a username hardcoded into your application. The users will not be able to get the username unless they have access to the code and even if they have access to the code, the password could be encrypted.

          C 1 Reply Last reply
          0
          • C Cormac M Redmond

            Thanks. Unfortunately, those techniques rely on username and password credentials. I need to prevent my users from being able to build their own applications andthen using my web service with their username and password. Regards, Cormac

            C Offline
            C Offline
            Christian Graus
            wrote on last edited by
            #5

            Your other option is to see if you can get the IP address of the incoming request, and validate it. Of course, your users can decompile your code and change any checks you do, so.....

            Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )

            C 1 Reply Last reply
            0
            • T Tarakeshwar Reddy

              Instead of using the username and password of the users, you can have a username hardcoded into your application. The users will not be able to get the username unless they have access to the code and even if they have access to the code, the password could be encrypted.

              C Offline
              C Offline
              Cormac M Redmond
              wrote on last edited by
              #6

              Thanks for your suggesstion. However, this is not a solution; it is too easy to decompile .NET applications. Encrypting a password just introduces another problem: the encryption key and how to 'hide' that. Hardcoding is not the answer. Unfortunately, I can't forsee any satisfactory solution.

              1 Reply Last reply
              0
              • C Christian Graus

                Your other option is to see if you can get the IP address of the incoming request, and validate it. Of course, your users can decompile your code and change any checks you do, so.....

                Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )

                C Offline
                C Offline
                Cormac M Redmond
                wrote on last edited by
                #7

                Yeah, plus my application needs to be usable from anywhere. I am implementing username/password authentication, but I'm worried my users could create their own application and utilise the web service (using their creddentials), and do some malicious things. In all honesty it'd probably never happen - but it's discouraging not to be able to solve this problem.

                C 1 Reply Last reply
                0
                • C Cormac M Redmond

                  Yeah, plus my application needs to be usable from anywhere. I am implementing username/password authentication, but I'm worried my users could create their own application and utilise the web service (using their creddentials), and do some malicious things. In all honesty it'd probably never happen - but it's discouraging not to be able to solve this problem.

                  C Offline
                  C Offline
                  Colin Angus Mackay
                  wrote on last edited by
                  #8

                  Then you have to defend your application from dodgy input. You have to ensure that your webservice is strict on validating the inputs. That will minimise any damage that may occur if someone does find a way through the authentication process.


                  Upcoming events: * Glasgow: Introduction to AJAX (2nd May), SQL Server 2005 - XML and XML Query Plans, Mock Objects, SQL Server Reporting Services... Never write for other people. Write for yourself, because you have a passion for it. -- Marc Clifton My website

                  1 Reply Last reply
                  0
                  • C Cormac M Redmond

                    Hi. I have a webservice - and I want to make sure that only MY application is using it. Is this possible, in a secure way? Thanks, Cormac

                    M Offline
                    M Offline
                    Mazdak
                    wrote on last edited by
                    #9

                    Other than these suggestions you can restrict accepting IP's from IIS: Property of Directory in IIS----> Directory Security----->Edit button in IP address and domain name restriction

                    Mazy
                    "This chancy chancy chancy world."

                    1 Reply Last reply
                    0
                    Reply
                    • Reply as topic
                    Log in to reply
                    • Oldest to Newest
                    • Newest to Oldest
                    • Most Votes


                    • Login

                    • Don't have an account? Register

                    • Login or register to search.
                    • First post
                      Last post
                    0
                    • Categories
                    • Recent
                    • Tags
                    • Popular
                    • World
                    • Users
                    • Groups