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
Remote Code Execution (RCE) System.Text.Encodings.Web 5.0.0 CVE-2021-26701 CWE-94
FROM mcr.microsoft.com/dotnet/aspnet:5.0-alpine AS base WORKDIR /app EXPOSE 80 EXPOSE 443
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
RUN apk upgrade musl
WORKDIR /app COPY --from=publish /app .
ENTRYPOINT ["dotnet", "SCV.Litmus.FinanceManagement.HttpApi.Host.dll"]
McAfee Antivirus reporting Volo.Abp.AuditLogging.HttpApi.Client.dll and Volo.Abp.IdentityServer.HttpApi.Client.dll as virus. Due to this we are not able to compile code. Kindly let us know how to resolve the issue.
ABP Framework version: v4.3.1 UI type: Angular DB provider: EF Core Tiered (MVC) or Identity Server Separated (Angular): yes
We have custom login page and using AWS SES for sending emails. Steps performed
Code added in Login components <a href="/account/forgot-password" class="forgot_pass_cl"> {{ 'AbpAccount::ForgotPassword' | abpLocalization }}</a>
When we click on Forgot Password? Its redirected to url http://localhost:4200/account/forgot-password
We are entering aws certified email on submit its calling api https://localhost:44359/api/account/send-password-reset-code The response of api is Status Code: 403 Forbidden JSON Response {"error":{"code":null,"message":"Can not find the given email address:Ish***** **@****s.com","details":null,"data":{},"validationErrors":null}}
Downloaded latest package Volo.Abp.Identity.AspNetCore package in Lit***.HttpApi project
Define this package in the LitHttpApiModule class in the LitName.HttpApi project
Added entry in Lit***.HttpApi.Host project appsettings.json "App": { "ClientUrl": "http://localhost:4200", }
ConfigureUrls options.Applications["Angular"].RootUrl = configuration["App:ClientUrl"]; options.Applications["Angular"].Urls[AccountUrlNames.PasswordReset] = "account/reset-password"; options.Applications["Angular"].Urls[AccountUrlNames.EmailConfirmation] = "account/email-confirmation";
Added ConfigureUrls To ConfigureServices() method in Lit***HttpApiHostModule class
Getting 403 Forbidden error, please advise.
ABP Framework version: 4.1.3 UI type: Angular Tiered (MVC) or Identity Server Seperated (Angular): yes Exception message and stack trace: Steps to reproduce the issue:
Creating a new ticket as the previous ticket is closed - https://support.abp.io/QA/Questions/536/How-to-Restrict-users-multiple-login-session
Steps performed as per recommendation -
What could be the reason for this behaviour even token is revoked and still we can access api’s?
Creating a new ticket to share more details as I cannot update the existing ticket - https://support.abp.io/QA/Questions/1352/Identity-server-token
ABP Framework version: v4.3.1 UI type: Angular DB provider: EF Core Tiered (MVC) or Identity Server Separated (Angular): yes
As part of web application assessment, there was an observation on No Session Timeout. The expiration of JWT was set to 365 days. Need to implement a server side approach which expires a user’s session after a predefined interval (15-20 mins) of inactivity. Kindly advise on how to do it with existing ABP code base in our application.
Creating a new ticket to share more details as I cannot update the existing ticket - https://support.abp.io/QA/Questions/1352/Identity-server-token
As part of web application assessment, there was an observation reported about JWT tokens.
The JSON web token (JWT) for your web application was not encrypted, allowing the data within it to be inspected with trivial effort. This revealed the email (username) and expiration date of the token.
Recommendation is to either -
I understand that this is not related to the framework and it is the subject of Identity Server but we don't have much control over it as the Identity server is integrated within the framwework itself. Can you guide us to remediate this issue based on recommendations mentioned above. Need to know what changes will be required in existing application code to handle it.
Thanks