Open Closed

TenantId is null after deploy the application to Azure kubernetes #5477


User avatar
0
DominaTang created

After deployed the application (Micro-Service template) to Azure Kubernates, Choose an tennant from login screen, however the tennantId is null while inspect the network traffic from browser. Local works fine.

Do you have any clue about the reason?

Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, and please use the search on the homepage.

If you're creating a bug/problem report, please include the followings:

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

4 Answer(s)
  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    hi

    You can check the requests of the changing tenant in-browser dev tools. also check the cookies.

  • User Avatar
    0
    DominaTang created

    Hi Ming,

    With Dev Tools, we check network traffic and cookies, current tenant's Id is null. That is why this ticket is raised. But Developer local debugging, everything seems fine.

    Thanks, Domina

  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    Can you share an online website? liming.ma@volosoft.com

  • User Avatar
    0
    DominaTang created

    Figured out the reason. It is because of wrong grand type setting (should use grand type "code", but the angular app users resource owner.

Made with ❤️ on ABP v9.1.0-preview. Updated on December 10, 2024, 06:38