Hi Berkansasmaz,
We can confirm that the solution provided works. Thanks.
Eric.
Hi @maliming,
Thanks for getting back to me.
At first glance, I don't see any application logs. /wwwroot/Logs is empty
I've also looked in the Application Event logs of Azure Web Services, but the last Error was from 2022/11/10 (which had to do with the certificates issues that plenty of people had, so that was easy to fix)
So my next question is: how to get to the ABP applications logs on Azure Web Service, because currently I'm not seeing them.
OK, this is what I was able to capture
This is still not fixed, so I want to re-open the ticket. I will try to redeploy on a new Azure Web Services instance. Nevertheless, I will not have a lot of time this week, so there won't be a lot of feedback from me the next couple of days.
Hi Li,
I don't believe you are answering my questions.
The error is a result of pushing the Check button:
The content I use is: Server=tcp:XXXXX-europe-1.database.windows.net;Authentication=Active Directory Default; Database=XXXXXX-dev-europe;
As you might know, www.connectionstrings.com does not give a good example of using System Assigned Managed Identity with SQL Azure
But on the Microsoft website there are some good instructions on how to setup Managed Identity with App Service. https://learn.microsoft.com/en-us/azure/app-service/tutorial-connect-msi-sql-database?tabs=windowsclient%2Cefcore%2Cdotnet#3-modify-your-project
And I'm using the connectionstring as defined in the example: "Server=tcp:<server-name>.database.windows.net;Authentication=Active Directory Default; Database=<database-name>;"
So my questions are still:
I would appreciate if you can give this some thoughts.
Hi,
We are sending our errors to Azure Application Insights, so we don't have a logfile.
BUT, it's even more weird: The test actually fails, but when hitting save, the database gets created. So there is definitely something wrong with that connection string check that doesn't take into account valid connectionstrings using Managed Identity syntax.
Hi,
Is there a specific reason why the initial catalog is replaced by master? in the connectionstring checker? https://github.com/abpframework/abp/blob/b23affb0ed225f020dc7b66aebc208acd71a1c01/framework/src/Volo.Abp.EntityFrameworkCore.SqlServer/Volo/Abp/EntityFrameworkCore/ConnectionStrings/SqlServerConnectionStringChecker.cs#L20-L21
Managed identities should not have access to master, they are database scoped credentials and only need to have access to the Database (or Initial Catalog) passed in the connectionstring.
ah OK. Thanks. We will upgrade soon.
Oh, but you didn't answer my question :-) Where should this code go? In each specific file? Can you please give an example?
I'm getting a message saying that I need to open the browser to login, but since this jobrunner is a standard devops agent, that is not possible
