Activities of "mrbrl"

• ABP Framework version: v8.0

• ABP Studio version: v0.6

• UI Type:Blazor WASM

• Database System: EF Core (SQL Server)

• Steps to reproduce the issue:

1. Opened ABP Studio and navigated to 'File > Initialize Existing Solution' to open a MicroService Template Solution initially generated with ABP Suite.
2. Observed that a new Web Project was added in the Solution Explorer.
3. Manually removed the new Web Project by editing the .abpmdl and .abpsln files.

Current Behavior:

• After the initialization , the Solution Runner tree remains consistently empty.
• All tabs within the Solution Runner (Overall, Browse, etc.) are empty when the solution is not running.
• The same empty state persists in the Solution Runner tree and tabs even when running the solution with Tye.

Expected Behavior:

• The Solution Runner tree should display relevant project components.
• Tabs within the Solution Runner (Overall, Browse, etc.) should show appropriate information and functionality, both when the solution is and is not running.

• ABP Framework version: v5.3.x
• UI type: Blazor Server
• DB provider: EF Core \
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace: Could not find IdentityClientConfiguration for AbpMvcClient. Either define a configuration for AbpMvcClient or set a default configuration. [23:31:00 INF] Authorization failed. These requirements were not met: PermissionRequirement: ...
• Steps to reproduce the issue:" Run the application. Occasionally, the UI as well as some Menu items does not render. after a few minutes or refreshes, it may resolve to normal The issue happens both in developments (all apps in same box) and prod ( 1 box per each app - IDS, Blazor Server WAF, Web API)

We disabled Redis (ie not using) We have seen the threads: https://support.abp.io/QA/Questions/2633/Could-not-find-IdentityClientConfiguration-for-AbpMvcClientWhy and https://support.abp.io/QA/Questions/1627/How-can-I-persist-ASPNET-Core-Data-Protection-Keys-to-the-database

Both do not provide enough details to be conclusive.

Could you let us know what may be the root cause of the issue? Is it possibly because we are not using Redis ?

Thanks.

**ABP Framework version: v5.3.0 Commercial

UI type: Blazor Server

DB provider: EF Core

Tiered : Blazor Web , IDS, web API**

Use Case:

Blazor Server App hosted in 'WebServer' Identity Server hosted in 'AppServer' End Users may only access 'WebServer'

With the default authentication flow and UI residing on Identity Server, when authenticating on Blazor Server App (on WebServer - which users can access), the flow redirects to Identity Server (on AppServer which users cannot access) - and therefore authentication cannot proceed.

The Authentication is leveraging both local (to IDS database), and LDAP (which defaults to local authentication when failing to connect) authentication.

What would solve the problem is to have the authentication UI on the Blazor Server App, which would leverage the ABP-fronted IDS APIs to allow login, logout, token issuance and refresh, cookie, and LDAP authentication.

I did not find any conclusive documentation on this and would be grateful for directions on this - as to avoid recreating a whole wheel.

Thanks a ton!

• ABP Framework version: v5.3.0 Commercial
• UI type: Blazor
• DB provider: EF Core
• Tiered

We are heavily relying on the IDS and LDAP integration in ABP, one of the main reasons we picked the framework. We attempted to update to the last 5.3.0 version today and noticed the LDAP integration has substantially changed, likely in anticipation to remove IDS from the platform. We have a number of projects relying on both IDS and LDAP and the prospect of having it possibly removed from the platform means that we won't be may not be able to update to future ABP versions.

Could you please let us know :

• What are the migration steps for LDAP in 5.3.x
• Is LDAP Integration here to stay in future ABP versions?
• Any plans to keep the IDS support option?
• Any plans for Commercial IDS support?

Thanks!

announcement below: *'We have announced the plan of replacing the IdentityServer. ABP currently uses IdentityServer4 to add OAuth features as built-in on the server-side. However, since IdentityServer4's support ends at the end of the year 2022. Its replacement is Duende IdentityServer, which is not a free software anymore. (see more)

Therefore, we've decided to completely drop the IdentityServer4 from the ABP platform and implement the OpenIddict and install onto the startup templates.

We've implemented both open source and commercial OpenIddict modules, we plan to remove Identity Server and replace it with OpenIddict for template projects in ABP v6.0. Please check #12084 to see the development made on the open-source side.

We're creating the documentation for the OpenIddict Module, if you want to have general knowledge about this module, you can check the documentation from here. Currently, this is a draft documentation but it gives overall knowledge about the OpenIddict Module, we'll complete this documentation in ABP v6.0 and you'll be able to read it completely.

Currently, we are also working on Keycloak integration possibilities in parallel to the OpenIddict integration research and we've prepared some samples that you can examine. You can see #154 and #158.'*