Activities of "epieters"

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:

• What am I missing?
• Which validations are done by the ABP Framework (Commercial) that I'm getting an error saying that my connectionstring is not valid? Its seems to come from Volo.Saas.Host.TenantAppService.CheckConnectionStringAsync(String connectionString)

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.

• ABP Framework version: v8.2
• UI Type: MVC
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): no
• Exception message and full stack trace:
• Steps to reproduce the issue:

It's not clear how and where to define the next and previous pages. Is this done in the doc-nav.json or in the page itself? Is this on the item itself?

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?

• ABP Framework version: v8.3
• UI Type: MVC
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): no

We are using ABP Commercial.

During the file import of users, we would also like to assign them to an organization unit. At the moment OU's is not foreseen as an import field.

Is there a workaround that for this?

Can you please consider this as a new feature for you commercial module? It's kind of strange that on one hand side you have a very flexible and good OU approach, but it's not possible to add users to the OU's in bulk.

Thanks.

Eric.

We are having ABP Commercial and are migrating from 8.2 to 9.1 As part of our CI/CD process in Azure Devops we were running:

1. abp login $(abpUser) -p $(abpPassword)
2. abp install-libs

But with the new version of the cli, it's no longer possible to use <user> and <password> on the commandline for abp login. Hence our CI/CD process is blocked.

Is there a solution for this problem?

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

Also tried with the --old switch, but that resulted in an error as well