Activities of "EngincanV"

ABP Suite most wanted feature has been implemented.
Your custom code will not be overwritten anymore
https://commercial.abp.io/releases/pr/14629

This is Amazing addition to Suite. Well done ABP Team.

Can ABP team create a customisation sample for us to learn for-example adding collection/List to RootEntity, Domain Services, EFcore and Application Services and then regenerate based code

Hi, we have an internal issue with creating documentation to highlight this feature. We will describe the customization process within an example.

Then if ABP suite is no longer going to allow this. Then the option should be removed. Because right now it appears that it DOES support installation of that theme.

Please refund the credit for my question.

Hi, we have removed the option from the modules page and it will be available in the next version. Your credit is refunded.

Regards.

Hi
When are you releasing new version?

Within this week. In the meantime, you can manually update the LeptonX package version.

Hi

Did you fix the bug? Still get LeptonX version 2.4.0-preview20230811 and build error.

If I manually change LeptonX version to 2.3.-, I can start up the application, but LeptonX logo not updated (no logo and brand name). See log in screen below

Yes, we have fixed the problem. But we need to release a new version to make it available and we'll make it asap.

You can try abp update and change the 2.4.0-preview20230810 to 2.3.*-* manually, it should work.

How about other packages? Still use v7.3.1? I found that all packages in all projects are not updated. Please, check this issue. Below is only example of one project file.

Hi, this PR needed to be merged before allowing you to successfully update your application. Please, retry to update again, it should successfully update now.

Hi, we have an internal issue to support the master/detail page in Suite. We aim to implement this feature in v8.0.

Can you share the following information?

• ABP Framework version: vX.X.X
• UI type: Angular / MVC / Blazor
• DB provider: EF Core / MongoDB
• And the properties of the entity that you are generating:

I fixed the problem by implementing another authentication schema, so in that way i can challenge the user to authenticate and when it is done i can sign in the user and redirect the user to the page.

Great to hear that you fixed the problem.

I didn't understand how i can pass the authorization header while i am redirecting the user from angular. Is there any sample code how to do that? I would be happy if you can share it.

Actually, I was just clarifying the flow in a normal situation. For your requirement, creating a new authentication scheme and challenging to login with redirect uri as /hangfire is a good approach I think. And i don't have any alternative to that approach for now.

Hello again, Thanks for the explanation, can i ask how can i do the same for hangfire dashboard? If i write a mvc controller action, how can i redirect the user to auth server log in page and then redirect to hangfire dashboard?

Hi, you can do this easily by redirecting to auth server and specifying the ReturnUrl as /hangfire (https://localhost:5000/Account/Login?ReturnUrl=https://localhost:5001/hangfire), however, even if you do that, you should pass the authorization header from auth server to your host application somehow, so a simple redirection would not be enough.

Ideally, you need to authenticate via your client application, retrieve the token, and use it in the authorization header in the subsequent calls that you'll make to the host application.

Hi, this is the expected behavior. Because, when you authorize through Swagger, in every request that you made through Swagger, an authorization header will be passed with the bearer token (ABP intercepts the call and pass the token, in the js side), and that makes you authorized.

However, if you navigate to the /hangfire page, you will see 401 status code, because there is not any authorization header in the request headers. You should set the authorization header with the bearer token in your request by yourself.