Tiered (for MVC) or Auth Server Separated (for Angular): yes
Exception message and full stack trace: There are no exceptions. The cookie is just not being saved, and because of that, we can't log in to the application. The solution works fine locally; it just doesn't work when deployed to the Kubernetes environment.
Steps to reproduce the issue:
Go to the Angular application, ex: https://angular.yourwebsite.com
Click on the logging button
You will be redirected to https://auth.yourwebsite.com
Input a valid user and password and click on the Login button
You should be authenticated and redirected to the https://angular.yourwebsite.com URL
Then in here, ideally you should be authenticated and able to navigate to the authenticated pages, but it's not
Checking the cookies on the locally run application, I can see that the .AspNetCore.Identity.Application cookie is being saved, but I can't see that on the published website at https://angular.yourwebsite.com, even though it's saving the cookie on https://auth.yourwebsite.com so if you click on the Log in button again it will detect that you are authenticated and redirect you back
Showing 1 to 1 of 1 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on December 13, 2024, 06:09