migration guide for ABP 10.0: https://abp.io/docs/10.0/release-info/migration-guides/abp-10-0 - There

hi `/signin-microsoft-workforce` `/signin-microsoft-workflow` Is there a spelling mistake?

maliming] said: > hi > > > `/signin-microsoft-workforce` > `/signin-microsoft-workflow` > > Is there

[image.png](/QA/files/3a1d19ced4921fa02289660523901bf7.png) Is there an example of this anywhere?

Now there is empty layout in use. Are these keys changed at your side? !

I noticed that in my code there is still some APP_INITIALIZER in use.

[image.png](/QA/files/3a1d1da8d43b46558ed1834091025066.png) So I was figuring out why there was not

Now after updates I managed to get UI open there is no side bar at left.

I noticed in browser that there is empty layout inside dynamic layout instead of application layout which

**Reusable Components** - There is no built-in ABP modal for creating language texts, but you can reuse

AbpButtonType.Primary ); }); }); Since the application is created using ABP Suite, there

manually running a rollback for each is unfeasible, is the approach to extend db migrator (why isnt there

a flag for this already) or to keep track of how many tenants there are and update a script rollback

ddocker\_mount\_appsettings.png](/QA/files/3a1d12d6f45d5aedf3044faf85cda3b4.png) even in the browser there

***ERROR TypeError: Cannot read properties of undefined (reading 'grant\_type')*** Is there something

There is no built-in ABP Angular mechanism to store access tokens in HttpOnly cookies, as this is a limitation

There is already an open issue to the improvement of token handling (for example, moving to an in-memory

- There is currently no built-in way in ABP to make the permission management UI automatically select

- There is no built-in mechanism to enforce or display permission dependencies in the permission

Hi there. Any way to get this behavior in the permissions modal?

Hi there.

If so, is there a way to implement permission dependencies in the way I described? Thanks!

There is no secure way to keep the Blazorise product token hidden from the client in a Blazor WebAssembly

. - There is no official ABP patch for this specific CVE, but keeping all third-party libraries up to

However, it appears that there is no active maintenance for the Select2 library at this time.

Is there any recommended workaround for this vulnerability, or does the ABP team have plans to replace

However, it appears that there is no active maintenance for the Select2 library at this time.

Is there any recommended workaround for this vulnerability, or does the ABP team have plans to replace

Is there a plan to address or patch this?

- There is no built-in ABP option to globally disable client-side validation for all proxies in WASM

api-version=1.0 - 400 0 null 4.8285ms ``` It says it's failing on a antiforgery token, but there are

There are two similar errors I'm encountering. 1.

There is an API call that uses `[DisableValidation]`, and it works normally when using InteractiveServer

Is there a way to disable this eager validation and wait until it hits the api? 2.

Is there a way t fix this or disable it?

**3) Overriding ABP Suite’s Scaffolding:** Is there a supported way to override or customize ABP Suite

Is there admin UI for it?

your `*HttpApi.Host` project and search for the `ConfigureAuthentication` method, then you'll notice there

I fixed your project and there is the **take-aways**: - Created 2 different client in the "MerkeziSSO

- There is a ClientSecret mismatch in Blazor project, I fixed it: - There is a ClientSecret

Is there anything else we need to configure to use centralized SSO?

. ## Root Cause Analysis Based on the ABP source code and the ticket conversation, there are several

There are three solutions: #### Solution A: Share the Same Database (Recommended for Monolith) Configure

Related issue: I also tried to use the dynamic proxy directly via the client API that already exists there

There is authentication issue. After adding reverse proxy using nginx, I see this issue.

There is authentication issue. After adding reverse proxy using nginx, I see this issue.

> https://localhost:44500/hostapi - host api > https://localhost:44500/auth - Auth Hi, it seems there

However, as of now, there is no dedicated page that explicitly lists End-of-Support (EOS) or End-of-Life

there is no docs about this, can support team assist us on this inquiry?