Activities of "Rishi1532"

Hi use the Sourcecode branch

Hi Made the Repo Private and invite sent as a contributor

Hello ABP Support Team,

We are facing issues with Domain-Based Tenant Resolution while using ABP Framework 9.0.4 (Angular + OpenIddict).

We followed the official ABP community article below **exactly **to implement the domain-based tenant resolver:

https://abp.io/community/articles/how-to-use-domainbased-tenant-resolver-in-abp-with-angular-and-openiddict-v9y8da7v

⚠️ Note: The sample source code provided in the article is based on ABP 10.0.2, while our application is using ABP 9.0.4.

Environment Details

• ABP Version: 9.0.4

• Frontend: Angular

• Authentication: OpenIddict

• Tenant Resolution: Domain-based tenant resolver

• Hosting: Localhost (custom domains) / Deployed environment

Source Code (Public Repository)

GitHub repository with full source code and configuration:

https://github.com/RISHI-KH-2611/Test/tree/sourcecode

We recreated a demo project in **ABP 9.0.4 **and followed the exact same implementation and steps as mentioned in the article and the sample project.

Public Deployed URL (For Testing)

https://dentpalqaaumtech.org/

• Username / Password: ABP default credentials

Issues Observed

1️⃣** Localhost + Custom Domains**

Issue: Infinite login redirect loop

Steps:

• Run the application locally

• Configure and access the app using custom domains

• Attempt to log in as a tenant user

Observed Behavior:

• Login page continuously redirects

• Authentication never completes

• Results in an infinite login loop

2️⃣** Deployed Environment**

Issue: Tenant users cannot log in (Host admin works)

Observed Behavior:

• Host Admin can log in successfully

• Tenant users are unable to log in

• Login either redirects back to the login screen or fails silently after authentication

Expected Behavior:

• Tenant users should be able to log in based on domain resolution

• Authentication flow should work consistently for both host and tenants

Request for Assistance

Could you please help us understand:

1. Whether domain-based tenant resolution behaves differently in ABP 9.0.4
2. If any additional configuration is required for Angular + OpenIddict in ABP 9.x
3. Whether this is a known issue or limitation in ABP 9.x
4. Recommended workaround or fix if upgrading to 10.x is the only solution

[maliming] said: hi

Issue 1: Host (Super Admin) Login Issue

Please check the debug logs see what happened?

https://abp.io/support/questions/8622/How-to-enable-Debug-logs-for-troubleshoot-problems

Can you also share an online URL and test user and password?

liming.ma@volosoft.com

Thanks.

we will update you with this details give us some time

[maliming] said: hi

You can configure OpenIddict to support wildcard domain names.

https://abp.io/docs/latest/framework/architecture/multi-tenancy#domainsubdomain-tenant-resolver

we have already added that but still the issue persistent

Hello ABP Support Team,

We are currently implementing domain-based tenant resolution and have been following the official ABP blog below for the implementation steps:

https://abp.io/community/articles/how-to-use-domainbased-tenant-resolver-in-abp-with-angular-and-openiddict-v9y8da7v#step-2-configure-http-for-local-development-optional

Environment Details

• Frontend: Angular

• Backend: .NET 9.0

• ABP Framework Version: 9.0.4

• Authentication: OpenIddict

• Multi-tenancy: Domain-based tenant resolver

Both the frontend and backend are running correctly, and the backend URLs are accessible for specific tenant domains.

However, we are facing the following two issues:

Issue 1: Host (Super Admin) Login Issue

We have renamed the Host Admin to Super Admin. When attempting to log in as the Super Admin:

• The login screen remains stuck and does not proceed further.

• If an incorrect password is entered, the error message is displayed correctly.

• This indicates that authentication validation is occurring, but the login flow is not completing successfully.

• The same behavior occurs when attempting to log in from the backend as well (i.e., Super Admin login is not working from either Angular or backend).

Issue 2: Tenant Login Issue via Angular (OpenIddict Error)

For tenant-specific domains:

• The tenant frontend loads correctly.

• However, when navigating to the login screen from the Angular frontend, an OpenIddict-related error occurs.

• This issue does not occur when accessing the login screen directly from the backend.

This behavior suggests a possible issue with OpenIddict, tenant resolution during the Angular-based login flow.

Could you please advise on:

The correct way to handle host users login when domain-based tenant resolution is enabled.

Any additional configuration required for Angular + OpenIddict login when using tenant subdomains.

Whether there are known limitations or required settings for this setup in ABP 9.0.4.

Please let us know if you need any additional details, logs, or configuration snippets from our side.

Thank you for your support.

Best regards, Rishikesh

Hello ABP Support Team,

I’m facing a critical issue while restoring NuGet packages for my ABP 8.3.4 project. Every time I run dotnet restore, I get the following repeated error:

NU1301: Unable to load the service index for source https://nuget.abp.io/nuget/v3/index.json. Response status code does not indicate success: 500 (Internal Server Error).

What I Have Tried: Cleared local NuGet cache: dotnet nuget locals all --clear Disabled ABP NuGet feed in NuGet.Config and re-enabled it Ran restore with --disable-parallel and --no-cache Confirmed the error is consistently coming from the ABP NuGet feed

My Project Details: ABP Version: 8.3.4 UI: Angular Backend: .NET 8 Operating System: Windows 10 ABP Feed URL: https://nuget.abp.io/nuget/v3/index.json

Please let me know if the ABP feed is currently having server-side issues or if there is a workaround to complete package restore and proxy generation. Thank you in advance.

Best regards, Rishikesh

Hi,

Thank you for the information.

We’ve collected the debug logs for issue #9502 – "Cypress POST Requests Returning 400 Bad Request – Works Fine in Browser" and have sent them directly via email to liming.ma@volosoft.com.

Please confirm once received. Let us know if any additional details are needed.

Thanks

Hi,

Thank you for the response.

We’ve enabled debug logging as per the instructions provided in this guide.

Could you please let us know the preferred way to share the debug log files with you for the 400 error issue we’re encountering?

Looking forward to your guidance.

Best regards, Rishikesh Tuniki

hi we have used the recommendations from the answer you have provided added this in the HttpApiHostModule > configureServices method Configure<AbpAntiForgeryOptions>(options => { options.TokenCookie.Domain = ".aumtech.org"; // Use your actual parent domain options.TokenCookie.SecurePolicy = CookieSecurePolicy.None; options.TokenCookie.SameSite = SameSiteMode.Lax; // or SameSiteMode.None if using HTTPS });

we still received the same error

and 4th point id not applicable as we are using data center Linux server for hosting