The above provides a database server, a database and also Integrated Security=true. And back in the day, it may have looked something like this:ĭata Source=myServer Initial Catalog=myDB Integrated Security=true When you seek to connect a web application to a database, you'll typically use some kind of database connection string. I speak of course, of our old friend Integrated Security=true.
This is generally a good thing, however in the excitement of the new, it's possible to forget some of the good properties that "on premise" deployment afforded when it came to connectivity and authentication. Few are the organisations that view deployment to data centers they manage as the future. Integrated Security=true Įveryone is deploying to the cloud. This post talks us through using managed identity for connecting to Azure SQL.
#DOES APEX SQL WORK FOR AZURE SQL PASSWORD#
Importantly, it allows us to avoid exposing our database to username / password authentication, and hence making it a tougher target for bad actors. Hence it has a good developer experience.
#DOES APEX SQL WORK FOR AZURE SQL CODE#
It's an approach that does not require code changes merely configuration of connection string and associated resources. Managed Identity offers a very secure way for applications running in Azure to connect to Azure SQL databases.
0 kommentar(er)
