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. Database & SysAdmin
  3. Database
  4. How to prevent the user from accessing database directly?

How to prevent the user from accessing database directly?

Scheduled Pinned Locked Moved Database
databaseoracletutorialquestionlearning
2 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.
  • F Offline
    F Offline
    fat888
    wrote on last edited by
    #1

    I have an application which is accessing a SQLServer and an Oracle. Of course, the application must know the password. I want to prevent the users from accessing the database directly. When they want to read/write data,they have to use my program. What can I do? Thanks. Hi guys. I'm a very fat man. Do you like fat men?

    A 1 Reply Last reply
    0
    • F fat888

      I have an application which is accessing a SQLServer and an Oracle. Of course, the application must know the password. I want to prevent the users from accessing the database directly. When they want to read/write data,they have to use my program. What can I do? Thanks. Hi guys. I'm a very fat man. Do you like fat men?

      A Offline
      A Offline
      Anonymous
      wrote on last edited by
      #2

      The typical way of doing this is exactly what you are talking about. You have a single logon/password which uses a somewhat complicated and unique name/password convention. All other DB accounts are locked out of the DB. The user could still access the DB directly, but they would need to know the userid/password. The other way you can do this is to encrypt the data in your DB. This is very difficult to do unless you have a library/toolkit for database access which does this for you. One way to do this is to use the digest MD5 algorithm on each and every column of data. This leads to serious problems though because it is not easy to query the DB and again, you need a library/toolkit that does the work for you.

      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