Activities of "gterdem"

Can you check if your gateway has websocket configuration as in the ocelot documentation in the OnApplicationInitialization method like:

app.UseWebSockets();
app.UseOcelot().Wait();

Hello,

This is a very broad deployment scenario to cover and deployment is not our borders to cover unfortunatelly.

We have provided deployment configurations for the eShopOnAbp (with angular back-office application) application with helm chart configurations that you can examine. You can find helm chart values for staging and azure environments at https://github.com/abpframework/eShopOnAbp/tree/main/etc/k8s/eshoponabp

If you have no knowledge about Kubernetess and Azure, I would suggest trying some basic tutorials about how to get started, it is not something we can provide.

Hi, you wrote fix it, but that is what i am asking you ! This is no help ...

I wrote you, that if i restart the appmicro-appzero the NoSql Error "AbpLocalizationResources" disapears..So after restart there is no error in the logs anymore...I dont know how to fix the error with "AbpLocalizationResources" .. Is it an issues with Nosqql ? A timing problem ? Why does this happen ?

In the blazor log is still this error:

PermissionRequirement: SettingManagement.Emailing [07:51:08 INF] Authorization failed. These requirements were not met: PermissionRequirement: AbpIdentity.SettingManagement [07:51:08 INF] Authorization failed. These requirements were not met: PermissionRequirement: AbpAccount.SettingManagement [07:51:08 INF] Authorization failed. These requirements were not met: ........

I dont think that the Blazor Authorization fails because of my appzero microservice. Instead it seem to be a generell problem, i did a test with a new microservice-template (7.0.1) and prepared production microservice.. after deployement to docker desktop it works, but after deployment to production kubernetes it produced the same errors like in my solution !

For the last kubernetes problem i did wait a long time before you could solve it:

https://support.abp.io/QA/Questions/3463/Helm-charts-for-533-and-Blazor https://support.abp.io/QA/Questions/3872/Abp-V600-Helm-Chart-Issues-and-deployment-errors-500400-during-login

So please check how you could help to solve this...I need your help. And again i would be great to take a detailed look with MS Teams to solve this...

We are preparing a production release for our customers, and now need to wait again till you could help to solve this.. We are losing time, which we need elsewhere..so please give this ticket a higher priority,

These are not error, they are information. Can you share error logs?

This was a bug and shoud've been fixed at version 7.0.1 patch. Can you try with the preview version?

I have refunded your question.

This is probably because of race condition for creating the database and seeding the data when the applications start running. Unlike Kubernetes where the pods automatically run again if it fails, it will stop the process and quit.

Try using up.ps1 first to get the infrastructural services up first (sql-server etc), then run the db migrator. Afterwards you can run the tye.

We made some improvements to make it more stable for tye development scenarios which will be released soon.

Can you check https://stackoverflow.com/a/70503191 if it’s working for you?

Your authority and the issuer doesn't match basically.

Expected issuer: https://authserver.domian.in Your issuer: http://authserver.jailocal.in/

You can set issuer at OpenIddictServerBuilder option:

PreConfigure<OpenIddictServerBuilder>(builder =>
{
    ...
    builder.SetIssuer(new Uri(configuration["AuthServer:Authority"])); //Should be "https://authserver.domian.in"
});

Your authserver MetaAddress should be http://authserver.jailocal.in/ which will be requested internally during token validation.

@thedatacrew

Can you share authserver module PreConfigureServices method please?

We’re still investigating.

The problem is about CustomSignInManager configuration is done before configuring the OpenIddictServer issuer.

Under PreConfigureServices:

PreConfigure<AbpOpenIddictAspNetCoreOptions>(options =>
{
    options.AddDevelopmentEncryptionAndSigningCertificate = false;
});

PreConfigure<OpenIddictServerBuilder>(builder =>
{
    builder.AddSigningCertificate(GetSigningCertificate(hostingEnvironment, configuration));
    builder.AddEncryptionCertificate(GetSigningCertificate(hostingEnvironment, configuration));
    builder.SetIssuer(new Uri(configuration["AuthServer:Authority"]));
});

PreConfigure<IdentityBuilder>(identityBuilder =>
{
    identityBuilder.AddSignInManager<CustomSignInManager>();
});

When the CustomSignInManager configured, Account/Login tries to redirect to initial appsettings configuration (localhost:44322) instead of overwritten issuer value.