I am trying to configure in grafana a sql server datasource with service principal authentication.
But I have seen that I only have these two options.
does anyone know any possibility to connect to sql server like in azure monitor?
I've been looking for information about it, but haven't found anything.
For security reasons I need to change the authentication that I have right now with SQL Server Authentication (user/pass) for service principal authentication.
Thanks in advance.
Related
I currently am using ejabberd connected to a Microsoft SQL Server database. I am using a SQL Server login with username/password, per the documentation here: https://docs.ejabberd.im/admin/configuration/database/#microsoft-sql-server
How can I configure the ejabberd SQL Server storage to use SQL Server integrated security instead? I've not found documentation yet to address this.
A couple of ideas I have are to have the ejabberd service run as a kerberos/AD account, and configure the sql_server option as an ODBC connection string and use the integrated security option. Or to define the sql_username as the integrated login name, but remove the sql_password option.
Has anyone else tried doing this?
I am trying to connect from a On Prem SQL Server to an Azure SQL Database. We are able to telnet & connect directly but when trying to create a Linked Server it fails if we use Domain Authentication. This works great using SQL Login.
I scrambled across multiple documentation but couldn't find much for authentication using a Domain Service Account.
Would someone know if this works & any documentation on the setup will be helpful. Thanks
Thank you #Conor Cunningham MSFT for the comment, posting it as the answer.
SQL DB doesn't support domain authentication as it is not part of your domain and Linked servers don't directly take AAD auth, you will have to supply a password as well.
Refer to this document for more information.
I have configured my sql server with an Azure Active Directory admin that is a service principal (app registration). Is it possible to use clientid/secret to connect from Sql Management Studio?
I have tried Azure Active Directory - password authentication but client id and secret did not work.
It works just fine from my C# code with the same id and secret.
As suggested by #junnas in the comment section we cannot connect to Azure SQL database with Service Principal in SSMS.
Please check this blog
Currently I have two Azure VM's, one for the ASP.NET application (VM1) and another with SQL Server 2017 (VM2).
At the moment, the application on VM1 connects to VM2's SQL Server using SQL Server authentication, but now I want to change it to Windows authentication. I found this on the Azure website about how to connect:
Virtual networks also enables you to join your Azure VMs to a domain. This is the only way to use Windows authentication to SQL Server. The other connection scenarios require SQL Server authentication with user names and passwords.
https://learn.microsoft.com/en-us/azure/virtual-machines/windows/sqlclassic/virtual-machines-windows-classic-sql-connect
But there is also a website forum ask to use Azure Active Directory domain in order to achieve this.
I am confused regarding this, can anyone help me with a description how to connect my VM1 application to VM2 SQL Server using Windows authentication?
We have a client who uses MS Access to manipulate data in their SQL Server DB. I know that we can set up SQL Server to authenticate using Active Directory. If we set this up, can they use their AD logins to connect to SQL Server through Access? How?
I tried Googling this, but to no avail. Any links or direction would be much appreciated. Thank you.
Also, please direct me to the correct place, if I should ask this question elsewhere.
Yes this should be pretty straight forward. You can use Windows Authentication to connect to sql server.
When establishing ODBC connection from your Client, The Wizard for connection configuration to SQL Server takes you to a page which gives you options to choose how you want to connect to SQL SERVER. There you can choose to use Windows Authentication or SQL Server Authentication. You can choose the Windows Authentication Option.
Now when a client tries to connect to the SQL Server their windows credentials will be used to authenticate the user. And obviously if they are on a network their AD Account will Authenticate them.
See below a snapshot from ODBC Data Source Administrator wizard when configuring connection to sql server.