Access SQL-Database via ODBC driver in LEAPWORK

Follow

Comments

3 comments

  • Avatar
    marc towersap

    why are you doing it as a user dsn?  wouldn't it make better sense to make it a system dsn?

    0
    Comment actions Permalink
  • Avatar
    marc towersap

    and what's the point of using a DSN if you are exposing the username/password anyway?  and I'm confused.  If you use a windows user to log into sql server, you don't need to expose your username/password (graphic in 5.1)?  whereas if it's a sql user, you have to use both the DSN AND expose it's username/password (graphic in 5.2)????  That is just BAD.  You should never expose a username/password, even if it's generic.  It'd fail security audits every time.  And again, then what's the point of even using a DSN?  

    If I set it up as a system DSN (logging in as myself but using a system DSN running as a generic user), will it still work??  because it should if it's connecting purely as a DSN, without the need to expose that username/password.

    I get it if you use a user DSN, but then if a fellow tester logs in, they too have to set up their own user DSN.  Why NOT make it work with a system DSN so it doesn't matter who logs in, they can still use the DSN to connect/query the database, it would just work for them?

     

    0
    Comment actions Permalink
  • Avatar
    marc towersap

    it seems to me a ODBC connection via DSN is a bad solution.  Why not create a small app like a windows service that runs as the appropriate user, then have your code call that service.  there's got to be a better way to connect to a database and run queries without having bare usernames/passwords.

    0
    Comment actions Permalink

Please sign in to leave a comment.