Base solution for your next web application
Starts in:
01 DAYS
01 HRS
01 MIN
01 SEC

Activities of "shipserv"

Hi Zony,

We tried running the same code locally and on the server where we have the docker setup. Cookie not picked up on the docker setup. Any idea why this is so?

Best regards,

JP Maniago

Hi Zony,

Noted on the TestController. We'll try it out and revert when we have the result.

Best regards,

JP Maniago

Hi Zony,

Good morning! Hope you are well.

Sure. Please try using TN-58715, Url is https://admin.shipservlabs.com

Just to add to my previous response.

  • Yes, we configured the TenantIdResolveKey in the module as per Abp documentation. And yes, it's consistent with the front-end.
  • Yes, there is a reverse proxy.
    • It NGINX in the new Docker setup. This is the reason why we changed the TenantIdResolveKey as NGINX might have an issue with the Original format (with the dot).

Best regards,

JP Maniago

HI Zony,

Here's the screenshot of the Request Header, I don't see the Abp TenantId

Yes, we've modified the TenantIResolvekey. We removed the dot to see if it will work. We've seen posts with similar issues and that worked for them. But on our side, it does not work.

Thanks zony. :)

Hi Support,

Good morning!

Just following up on this. Any updates?

Regards,

JP

Hi Zony,

please see screenshots below, hope this helps

Regards,

JP

Hi Zony,

Yes, we think it is. Hope you can reprodue it asap as we are quite tight with the deadline.

Here are the base docker images we use for frontend. FROM node:10-alpine AS build-stage FROM nginx:alpine

and, FROM mcr.microsoft.com/dotnet/core/sdk:2.2 for backend

We tried this approach https://support.aspnetzero.com/QA/Questions/7642/Nginx-and-AbpTenantId-TenantIdResolveKey-Issue but problem still exists on "Login as Tenant" with backend error as seen in the stacktrace above.The tenantId is still missing from the session.

<br> Another issue we've seen so far is during switching tenant as seen below. The GetCurrentlyLoginInformation() returns "tenant":null as a response after successful switch. This is working on our existing environment (not docker).

Please keep us posted. Thank you!

Regards, Allan

hi Zony,

It's not related to Redis upon further investigation. Because we tested the codes with Redis on different environment (not docker) and it worked fine.

Regards, Allan

hi Zony,

Yes, that's right. So that all sensitive data such as database connection string will be stored on environment variables rather than in codes of appsettings.json. We don't want these configs to be hardcoded.

Regards, Allan

Showing 11 to 20 of 21 entries