Activities of "ilker.sungur"

I want to upgrade my project to latest abp version. Existing abp version: 9.0.5

First, i successfully updated Volo.Abp.Studio.Cli and Volo.Abp.Suite to the latest version. Then i tried runnig "abp update" command in project root folder.

I am getting console messages that almost all packages is up to date (except LeptonX and Volo.Abp.Studio.Client.AspNetCore)

• ABP Framework version: v8.3.1
• UI Type: MVC
• Database System: EF Core (PostgreSQL)
• Tiered (for MVC) or Auth Server Separated (for Angular): no
• Exception message and full stack trace:
• abp login [user.name] [19:22:37 INF] You are running the second generation of the ABP CLI. If you're interested in the legacy CLI, see https://abp.io/new-cli [19:22:37 WRN] 1. HTTP request attempt failed to https://abp.io/api/license/check-multiple-organizations?username=[user.name] with an error: 403-Forbidden. Waiting 2 secs for the next try... [19:22:39 WRN] 2. HTTP request attempt failed to https://abp.io/api/license/check-multiple-organizations?username=[user.name] with an error: 403-Forbidden. Waiting 4 secs for the next try... [19:22:43 WRN] 3. HTTP request attempt failed to https://abp.io/api/license/check-multiple-organizations?username=[user.name] with an error: 403-Forbidden. Waiting 7 secs for the next try... System.Exception: ERROR: Remote server returns 'Forbidden' at async Task Volo.Abp.Cli.Auth.AuthService.CheckMultipleOrganizationsAsync(string username) at async Task Volo.Abp.Cli.Commands.LoginCommand.Hqh5Vq0Ghf(CommandLineArgs , string ) at async Task Volo.Abp.Cli.Commands.LoginCommand.ExecuteAsync(CommandLineArgs commandLineArgs) at async Task Volo.Abp.Studio.Cli.StudioCliService.RunInternalAsync(CommandLineArgs commandLineArgs) at async Task Volo.Abp.Studio.Cli.StudioCliService.RunAsync(string[] args) Unhandled exception. System.Exception: ERROR: Remote server returns 'Forbidden' at Volo.Abp.Cli.Auth.AuthService.CheckMultipleOrganizationsAsync(String username) at Volo.Abp.Cli.Commands.LoginCommand.Hqh5Vq0Ghf(CommandLineArgs , String ) at Volo.Abp.Cli.Commands.LoginCommand.ExecuteAsync(CommandLineArgs commandLineArgs) at Volo.Abp.Studio.Cli.StudioCliService.RunInternalAsync(CommandLineArgs commandLineArgs) at Volo.Abp.Studio.Cli.StudioCliService.RunAsync(String[] args) at Volo.Abp.Studio.Cli.Program.LaxYuWdfb(Object ) at Volo.Abp.Studio.Cli.Program.(String[] args)

Other login command: abp login [user.name] --organization [OrganizationName] [19:24:42 INF] You are running the second generation of the ABP CLI. If you're interested in the legacy CLI, see https://abp.io/new-cli Password: [19:24:47 ERR] Could not retrieve the OpenId Connect discovery document! ErrorType: Http. Error: Error connecting to https://account.abp.io/.well-known/openid-configuration: Forbidden

Alternative to Organization name, i have tried with organizationId the result is same, like below:

abp login [user.name] --organization [11111-11111-1111-45a2-39fc9f8a1bd0] -> [OrganizationId from https://abp.io/my-organizations/....................] [19:25:58 INF] You are running the second generation of the ABP CLI. If you're interested in the legacy CLI, see https://abp.io/new-cli Password: [19:26:04 ERR] Could not retrieve the OpenId Connect discovery document! ErrorType: Http. Error: Error connecting to https://account.abp.io/.well-known/openid-configuration: Forbidden

• I have uninstalled all abp related tools and re-install the Volo.Abp.Studio.Cli latest version and tried again, result is same.

• I have tried deleting .-license.bin files, result is same too.

• I have not had any problems until today, but today I cannot use my abp commercial account.

• Steps to reproduce the issue: When i am trying to login to abp commercial account, i am getting error.

• ABP Framework version: v4.3.3
• UI type: MVC
• DB provider: EF Core / Postgres
• Microservice Template: Yes

We created a project with microservice commercial template and deployed project to Azure Kubernetes Services. All applications, services and gateways running with no error stand-alone. At authserver ui, user can successfully sign in. But, when backoffice application (management application created with MVC razor UI) trying to access authserver for authentication, request forwarded to authserver successfully and then with correct cridentials, authhentication completed successfully but when returning back to the backoffice web application (signin-oidc) there is no action and no redirect to the Backoffice web application. We contolled OIDC urls many times, and at local development environment it works successfully. There is no such error on IIS deployment. We did the OnApplicationInitialization code updates at AuthServerModule described the documentation: https://docs.abp.io/en/commercial/latest/startup-templates/microservice/applications#running-authserver-on-kubernates-pods Authserver and backoffice web application have SSL config.

How can we solve this problem?

Thanks for your help.