Activities of "epieters"

Getting an abp login error after upgrading to 9.1.2

Thanks, that will work for us ;-)

Will you continue to support the old CLI? Or is this something that will disappear?

See my answer above.

This works for the moment: dotnet tool install -g Volo.Abp.Cli As it installs the latest (old) CLI.

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

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

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?

• 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.

Oh, but you didn't answer my question :-) Where should this code go? In each specific file? Can you please give an example?

ah OK. Thanks. We will upgrade soon.