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. Double hop issue

Double hop issue

Scheduled Pinned Locked Moved ASP.NET
windows-adminasp-nethelpcsharpdatabase
3 Posts 2 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.
  • A Offline
    A Offline
    azam316
    wrote on last edited by
    #1

    I am having a double hop problem when i connect to an SQL Server located on a different machine through my asp.net application, when i use windows authentication on SQL SERVER. My IIS Authentication is also set to integerated windows authentication. The appliction is on Windows Server 2003. I have resolved this by using impersonation: in the web.config. And it works fine! The problem is that i the user id and password are in plain text which is pretty insecure! I can use the "Aspnet_setreg.exe" utility to keep the credentials in the registry...but the client is not agreeing upon it! I have also tried creating an impersonating context through the code but it did not work...dont know why? Please guide me if there is any way to do this in a secure way! thanx in advance! ☺«««DTA»»»☺

    J 1 Reply Last reply
    0
    • A azam316

      I am having a double hop problem when i connect to an SQL Server located on a different machine through my asp.net application, when i use windows authentication on SQL SERVER. My IIS Authentication is also set to integerated windows authentication. The appliction is on Windows Server 2003. I have resolved this by using impersonation: in the web.config. And it works fine! The problem is that i the user id and password are in plain text which is pretty insecure! I can use the "Aspnet_setreg.exe" utility to keep the credentials in the registry...but the client is not agreeing upon it! I have also tried creating an impersonating context through the code but it did not work...dont know why? Please guide me if there is any way to do this in a secure way! thanx in advance! ☺«««DTA»»»☺

      J Offline
      J Offline
      Javier Lozano
      wrote on last edited by
      #2

      Use HTTPS for the transfer protocol. ~Javier Lozano

      A 1 Reply Last reply
      0
      • J Javier Lozano

        Use HTTPS for the transfer protocol. ~Javier Lozano

        A Offline
        A Offline
        azam316
        wrote on last edited by
        #3

        HTTPS a good solution, but its not an option! I cant use it as its not acceptable to the client. Do you have any other solution? Please tell me if you have!!! Still thanx a lot! ☺«««DTA»»»☺

        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