I have a secure SQL DB that contains user data that is needed for login authentication by a web app. The web app is being developed by a third party, and we do not want to allow their app to authenticate login data with our secure DB directly.
What is the best approach to provide the authentication (verify the user is in our DB) without allowing a direct connection to our server and DB? The only thing I can think of is to develop a Windows 'service' that would run all the time and look for inbound login request packets. Then the 'service' would query the DB and return a 'pass/fail' packet for subsequent pickup by the web app.
I am sure there are a number of approaches, but I can think of only the one.
Alternatively, you could house the SP's on a separate server that has a connection to the target DB and the SP's would, in effect, be using a separate connection string to get to the actual data.
In this expert guide, you’ll learn about the components of a Modern Data Center. You will use cases for the value-added capabilities of Veeam®, including combining backup and replication for VMware disaster recovery and using replication for data center migration.
You can of course define an array to hold data that is of a particular type like an array of Strings to hold customer names or an array of Doubles to hold customer sales, but what do you do if you want to coordinate that data? This article describes…
Get people started with the process of using Access VBA to control Outlook using automation, Microsoft Access can control other applications. An example is the ability to programmatically talk to Microsoft Outlook. Using automation, an Access applic…
This lesson covers basic error handling code in Microsoft Excel using VBA. This is the first lesson in a 3-part series that uses code to loop through an Excel spreadsheet in VBA and then fix errors, taking advantage of error handling code.