Activities of "scottie.tang@cpy.com.hk"

• ABP Framework version: v8.X
• UI Type: Blazor Server
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): yes

We have a legacy system that needs to call an HTTP API within our system, which is built on the ABP.IO framework. Currently, the default authentication method in ABP.IO involves using Client ID/Secret to authenticate the API calls.

However, we want to implement a long-lived token approach for authentication. The idea is to have a hard-coded token in the legacy system, which will be used consistently for making API calls, rather than relying on Client ID/Secret. Is this possible?

Could you please provide me with guidance on how to achieve this long-lived token authentication in the ABP.IO framework? Specifically, I would like to know the recommended approach and any necessary configurations or code modifications that need to be made.

Thanks.

• ABP Framework version: v3.1.0
• UI Type: MVC
• Database System: MongoDB
• Tiered (for MVC) or Auth Server Separated (for Angular): yes

Hi Support,

We have recently completed the migration of our application from ABP 3.1.0 to 7.4. During the process, we encountered an issue with our old UploadController, which is an additional Web API controller responsible for handling file uploads via a simple POST request. While this code worked fine in version 3.1.0, it seems to be causing problems in the upgraded version.

I would greatly appreciate your advice or guidance on this matter. Is there any specific configuration that needs to be done in the WebModule or any other steps we should take to ensure the proper functioning of the UploadController in ABP 7.4?

Thank you for your assistance.

Below is our code snippet. ( We put the code in Controllers in HttpApi )

using Microsoft.AspNetCore.Hosting;
using Microsoft.AspNetCore.Http;
using Microsoft.AspNetCore.Mvc;
using System;
using System.Collections.Generic;
using System.IO;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using Volo.Abp.AspNetCore.Mvc;

namespace TEST.Controllers
{
    public class UploadController : AbpController
    {
        private readonly IWebHostEnvironment _hostingEnvironment;
        public UploadController(IWebHostEnvironment hostingEnvironment)
        {
            _hostingEnvironment = hostingEnvironment;
        }

        [HttpPost("UploadFile")]
        public async Task<JsonResult> UploadFile([FromForm] IFormFile file)
        {
            try
            {
                var webRootPath = _hostingEnvironment.WebRootPath + "\\Uploads\\";
                var folderPath = Guid.NewGuid() + "/";
                var fullFolderPath = webRootPath + folderPath;
                System.IO.Directory.CreateDirectory(fullFolderPath);
                var fullFilePath = fullFolderPath + file.FileName;
                using (var stream = new FileStream(fullFilePath, FileMode.Create))
                {
                    await file.CopyToAsync(stream);
                }

                return new JsonResult(new
                {
                    Success = true,
                    FileName = "/Uploads/" + folderPath + file.FileName
                });
            }
            catch
            {
                return new JsonResult(new
                {
                    Success = false
                });
            }
        }
    }
}

Hi Anjali,

Thanks for your reply.

From the migration guide, I can see that there are several "version to version" guide.

7.3 to 7.4 7.2 to 7.3 7.1 to 7.2 7.0 to 7.1 6.0 to 7.0 5.3 to 6.0 5.2 to 5.3 5.1 to 5.2 4.x to 5.0 4.2 to 4.3 4.x to 4.2 3.3.x to 4.0 2.9.x to 3.0

So if my application version is 3.1, does that mean i have to go through 3.3.x to 4.0, then 4.x to 5.0 and so on ? May i have some guidance/direction please? thank you.

Regards, Scottie

• ABP Framework version: v3.1
• UI Type: MVC
• Database System: MongoDB
• Tiered (for MVC) or Auth Server Separated (for Angular): yes

Dear Sir,

We are considering upgrading one of our application from abp framework version 3.1 (MVC+MongoDB) to 7.4 (BlazerServer+Mongo) and would greatly appreciate your expert consultation.

Should we proceed with the upgrade (if possible?) or consider a code rewrite? How compatible is our codebase with the latest version? What effort is required for the upgrade?

Thank you for your support.

Best regards, Scottie

Hi.

This problem is not occured if I create a new project of 7.2.0.

Our project is upgraded from 5.X to 7.2.0. After upgrade, some of our users receive "Unauthorized" message. The only thing they can do is click "OK" and re-login.

Before the upgrade, it appears that some users did not log out of their accounts. As a result, we suspect that their tokens were carried over to the new version and might have become invalid after the upgrade.

Could this issue be related to the upgrade from IdentityServer to OpenIdDict? Or other issues? Please kindly advise, thanks!

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

Hi, after we recently upgrade our project's ABP framework from 5.X to 7.2.0. We found that some users are having "Unauthorized" error message when they are accessing some of my functions, the only temporary solution/workaround is to logout and login again. (We just guess that the users maybe carrying some expired/invalid tokens in their browser.)

1. Do you have any advises on how to solve this issue?
2. Could we force user to logout when unauthorized access is detected? If yes, any way to do it ? ( force user to logout )

Thanks.

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

Dear ABP.IO Support Team,

Hi, our team has been using your framework version 5.0.2 along with the original Lepton theme for our projects. We are now considering upgrading to the latest version 7.2, especially since you have announced the release of the LeptonX theme, which appears to be a superior version.

However, we have a few questions before we proceed with the upgrade. Our projects are not UI-intensive, and we would like to know if there is any long-term support or status update on the original Lepton theme. If we decide to stick with the old theme, will we still receive support or be informed if ABP.IO plans to deprecate the original Lepton theme in the future?

Furthermore, we would like to know if it is worth upgrading to LeptonX now, given our project's requirements and the fact that it is not UI-intensive.

We appreciate your help and guidance in this matter and look forward to hearing from you soon.

Hi thanks, we are able to create a reversed proxy and add real IP to the request headers. We can retrieve the visitor IP address from those headers, however we want to know is there anything we need to apply/implement in abp modules in order to let us get remote ip via context.RemoteIpAddress ?

Thanks.

Thank you.

Hi,

I have deployed the same project to a dedicated server. It has the same result (slow). I do not think it is a CPU related issue, because at version 4.X, the speed is significantly faster. (same server machine)

Please help.

Many Thanks.