We have developed an ASP.Net application which we wish to put on our IIS. This IIS is on the intranet the other side of the firewall.
The problem we are grapling with is how we allow the application to talk to our back end databse via ODBC o don't we?
Do we allow an open channel to the database? What about hackers?
Do we replicate the database and put it on IIS on the Intranet? It's a large database!!!
Can we tell IIS just to allow communication between a specific PC through the firewall?
Authentication of the users we can do but the dilema we have is that the application needs to talk to Oracle via ODBC so where do we put this data?
Leave it where it is now and open a channel for ODBC to communicate or put it the other side of the firewall?
Any articles/sites about this topic and any other help greatly appreciated.
Regards,
CAB
The problem we are grapling with is how we allow the application to talk to our back end databse via ODBC o don't we?
Do we allow an open channel to the database? What about hackers?
Do we replicate the database and put it on IIS on the Intranet? It's a large database!!!
Can we tell IIS just to allow communication between a specific PC through the firewall?
Authentication of the users we can do but the dilema we have is that the application needs to talk to Oracle via ODBC so where do we put this data?
Leave it where it is now and open a channel for ODBC to communicate or put it the other side of the firewall?
Any articles/sites about this topic and any other help greatly appreciated.
Regards,
CAB