Could you please provide example/sample code for the above mentioned IBasicRepository Implementation?

IdentityRoleRepository.ToEfCoreRepository

Hi Team,

IdentityRoleRepository.ToEfCoreRepository throwing an error after abp upgrade to 6, below is the screen shot for the same.

Please provide the solution for this asap.

Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.

If you're creating a bug/problem report, please include followings:

• ABP Framework version: vX.X.X
• UI type: Angular / MVC / Blazor
• DB provider: EF Core / MongoDB
• Tiered (MVC) or Identity Server Separated (Angular): yes / no
• Exception message and stack trace:
• Steps to reproduce the issue:"

Hi Thanks for your reply, but some of the ABP Interfaces doesn't contain the definition for GetQueryableAsync() also (attached screen shots), how to do handle this kind of errors?

Hi Team,

I am getting below exceptions after migration the abp version to 6.

Please refer attached images and let me know the correct resolution for this.

errors mostly related to the namespace - Volo.Abp.Identity

Please provide the resolution asap.

Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.

If you're creating a bug/problem report, please include followings:

• ABP Framework version: vX.X.X
• UI type: Angular / MVC / Blazor
• DB provider: EF Core / MongoDB
• Tiered (MVC) or Identity Server Separated (Angular): yes / no
• Exception message and stack trace:
• Steps to reproduce the issue:"

Hi Team,

My current application is using abp version 4.3.1, and the documentation is available (4.x-5.2, 5.x- 5.2, 5.2-5.3, 5.3-6) for these versions. Now my query is Can I upgrade directly from 4.3.1 to 6.0 straight away?

Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.

If you're creating a bug/problem report, please include followings:

• ABP Framework version: vX.X.X
• UI type: Angular / MVC / Blazor
• DB provider: EF Core / MongoDB
• Tiered (MVC) or Identity Server Separated (Angular): yes / no
• Exception message and stack trace:
• Steps to reproduce the issue:"

Hi,

Would like to know if ABP.IO has any Rule Engine integrated with the framework? If not, is there any plan to integrate rule engine in future roadmap? Please share any support documentation in case you have to integrate Rule Engine with ABP.IO.

Thanks

The System.Text.Encodings.Web package is owned by Microsoft and used by the ABP Framework. See the reference github.com/abpframework/Volo.Abp.Core.csproj.

You can update it in your project to the latest version 5.0.1 Install-Package System.Text.Encodings.Web -Version 5.0.1

As I mentioned earlier, we don't refer to System.Text.Encodings.Web package directly into our project. It seems an indirect dependency into our project through Volo.Abp.Core library. Please suggest -

1. Which version of Volo.Abp.Core package should be used/upgraded in project to mitigate the dependency. Currenlty, we are using version 4.3.1 OR
2. Will directly referrring/updating our project to use System.Text.Encodings.Web package resolve the issue.

• ABP Framework version: v4.3.1
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace:
• We have recently upgraded our project to .Net 5.0 and ABP framework version 4.3.1. During source code scanning by Snyk.IO tool, it is reporting below vulnerability in our projects. There is no direct reference of the package "System.Text.Encodings.Web" in our projects, so not sure if the ABP framework code is using this library and is not updatee. Could you please advise, how it can be resolved - thru ABP version upgrade or something else?

Remote Code Execution (RCE) System.Text.Encodings.Web 5.0.0 CVE-2021-26701 CWE-94

• Also added the Dockerfile content of one of the projects which gets deployed in container

• Use Alpine Base Image

FROM mcr.microsoft.com/dotnet/aspnet:5.0-alpine AS base WORKDIR /app EXPOSE 80 EXPOSE 443

Use Alpine Base Image

FROM mcr.microsoft.com/dotnet/sdk:5.0-alpine AS build WORKDIR /src COPY . . WORKDIR "/src/SCV.Litmus/aspnet-core/microservices/SCV.Litmus.FinanceManagement.HttpApi.Host"

RUN dotnet restore RUN dotnet build -c Release -o /app

FROM build AS publish RUN dotnet publish -c Release -o /app

FROM base AS final

upgrade musl to remove potential vulnerability

RUN apk upgrade musl

WORKDIR /app COPY --from=publish /app .

ENTRYPOINT ["dotnet", "SCV.Litmus.FinanceManagement.HttpApi.Host.dll"]

• ABP Framework version: v4.3.1
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace:
• Steps to reproduce the issue:"
• Does ABP.IO framework provides integrated Azure AD integration for managing user identities and RBAC?
• If not, is there any plan to integrated Azure AD in future and by when it will be available, please advise.

• ABP Framework version: v4.3
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace:
• Steps to reproduce the issue:" We have a requirement to implement Single Sign-on feature into our application. The users are authenticated into another application which is non ABP.IO and from there they should be able to access our application (built in ABP.IO) using Single Sign-on feature (without login again). How can this be achived in ABP.IO framework, please advise and share solution steps.