Activities of "ESTeam"

Thanks

In this case, 1st option i put http://localhost:4200 and the second option http://localhost:4200/logout right?

I applied your solution but I'm getting this error. Has this happened to you before?

AADSTS9002326: Cross-origin token redemption is permitted only for the 'Single-Page Application'

I'm using these settings

yes

I supposedly did this but the English message continues to appear. I even put it in abpWeb.xml in Portuguese and it gives the idea that you are not using this because the message always appears "An error has occurred!"

Hi,

the problem (the last one reported in Azure Front Door) is resolved, the solution is here (#6 Overwrite ‘Host’ server variable on Windows IIS Web Apps, with applicationHost.xdt and Web.config): https://www.patrickob.com/2022/04/06/azure-front-door-afd-app-gateway-app-service-unexpected-issues/

Therefore, we no longer need to modify the request header.

thank you, Dirceu

Hi,

We already change to Azure Front Door and now we can change the language but when we call the method https://plano-mais-cuf-api-dev.sistemasaude.pt/AbpUserConfiguration/GetAll?d=1709222850822 is not returning the tenant id so regardless of the address it is always redirecting to the host: Host = https://host-dev.sistemasaude.pt Tenant 1 (default) - https://default-dev.sistemasaude.pt Tenant 2 (plano-mais-cuf) - https://plano-mais-cuf-dev.sistemasaude.pt

in the development environment (with azure front door):

in the UAT environment (with Gateway) - https://plano-mais-cuf-api-uat.sistemasaude.pt/AbpUserConfiguration/GetAll?d=1709223616322:

Do you have any tips on what could be causing this as this problem did not occur when using the Gateway? Both environments are equal in terms of code deployed and databases are also equal.

best regards, Dirceu

Hi,

Thanks. Is it possible to access your solution somehow ? It would be nice for us to test this using your project.

The source code? i've been testing localy We are currently changing the Azure environment to use Azure Front Door instead of Application Gateway. After testing (If the tests run successfully), it may no longer be necessary to modify the name of the request header ".AspNetCore.Culture" - We can wait and see if it works.

Hi @ESTeam

Just to be sure, you only have this problem for the not loggedin users, is that correct ?

Hi,

I've tested again now and after the login it only works if i open a new private window in the browser (Edge) - In chrome never works (even if you open a new incognito window). Before login never works.

Hi,

In that case, you can change the cookie name in language-switch.component.ts

Hi,

I tried one of 2 things and neither of them worked on the login page (after doing the login both solutions worked):

1. I changed the name of the cookie on the server side from “.AspNetCore.Culture” to “AspNetCoreCulture”, as you indicated. On the client side, I set the cookie in language-switch.component.ts component (and also changed the name in file AppPreBootstrap.ts):
2. I changed the name of the cookie on the server side from “.AspNetCore.Culture” to “AbpLocalizationCultureName” (this is another cookie used by ASP.NET Zero that was previously modified (because of the "." in the cookie name that had to be removed) from Abp.Localization.CultureName to AbpLocalizationCultureName). On the client side, I changed the name in file AppPreBootstrap.ts

I also tried changing the cookie whenever I send the language in the request header but it didn't work on the login page either:

The 2 cookies are with the "en" culture but the site remains in "pt-PT":

The request header is also in "en":

best regards, Dirceu