你好 请把三个网站的日志文件发送到 liming.ma@volosoft.com
谢谢
ok, Thanks. I will check it asap.
hi
Maybe the index error causes the system to cache the wrong data.
You can try removing the await OpenIdApplicationRepository.GetListAsync(); from the index page and testing again.
hi
I got your point.
You have to program to implement it, because the default MultiTenantConnectionStringResolver/DefaultConnectionStringResolver cannot determine the current situation, it can only return the default connection string.
https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.MultiTenancy/Volo/Abp/MultiTenancy/MultiTenantConnectionStringResolver.cs#L32
https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.Data/Volo/Abp/Data/DefaultConnectionStringResolver.cs#L29-L44
Can I check it remotely?
You can join zoom and share your screen.
Thanks https://us05web.zoom.us/j/85168939409?pwd=kcvNAdPxtvVlFdbCYgaOA3GTEg4aRE.1
hi
But we can specify an alternate connection string for the tenant upon creation and that works as intended
What do you mean by that? Can you describe it?
Thanks
Even if you use plain asp net core web application you need to solve the HTTPS problem. It has nothing to do with abp.
https://learn.microsoft.com/en-us/aspnet/core/security/enforcing-ssl?view=aspnetcore-8.0&tabs=visual-studio%2Clinux-ubuntu#require-https
I recommend using HTTPS. Otherwise, there may be a lot of related problems. HTTP is also unsafe.
You can get a free HTTPS for your website.
hi
HTTP 400 is about the Openiddict.
[INF] Client validation failed because 'https://esv2-test.azurewebsites.net/signin-oidc' was not a valid redirect_uri for ESv2_BlazorWebAppTiered.
[INF] The authorization request was rejected because the redirect_uri was invalid: 'https://esv2-test.azurewebsites.net/signin-oidc'.
