Activities of "gterdem"

This seems pretty much related to web server (IIS in this case) instead of ABP.

You can try IIS Request filtering. Also, there is an SO answer related to this.

Make sure you have Nuget.Config file commercial nuget source:

<configuration>
  <packageSources>
    <add key="ABP Commercial NuGet Source" value="https://nuget.abp.io/SOME_GUID/v3/index.json" />
  </packageSources>
</configuration>

There is no event receive order. It is very much against the nature of async communication.

If you have a process that needs to be done sequentially, you can use HTTP calls awaiting each other.

I think you should provide a way to create new clients, like angular and react native for microservice template, maybe throw the abp cli as new requirement

Thank you for your suggestion. I will create an internal issue related to this feature.

Https redirection is based on the webserver you are using. eShop is hosted on azure kubernetes cluster. You can check forced ssl-redirection: https://github.com/abpframework/eShopOnAbp/blob/d261dd9c4f36ce68790458980d9c7b4fbe2fb268/etc/k8s/eshoponabp/charts/authserver/templates/authserver-ingress.yaml#L7

You can google it if you are using IIS or Nginx for more accurate information.

On screenshot 3 you get 500 error. Can you share the related error logs of azureappapi-staging. The logs can be found under the Logs folder with the name logs.txt

Browsing to https://auth.mycompany.net I still get The cookie 'XSRF-TOKEN' has set 'SameSite=None' and must also set 'Secure'.

It seems related to HTTPS redirection.

You can update your cookie configurations in your authserver application Module ServiceConfiguration:

...
.AddCookie("Cookies", options =>
{
    options.ExpireTimeSpan = TimeSpan.FromDays(365);

    options.Cookie.HttpOnly = true;
    options.Cookie.SameSite = SameSiteMode.None;
    options.Cookie.SecurePolicy = CookieSecurePolicy.Always;
})
...

See more about working with sameSite cookies.

However it is recommended to use the authentication server on https.

Redirection from http to https in authserver web-server configuration should fix this problem.

Try

public virtual Task<IActionResult> OnGetAsync()
{
    return Task.FromResult<IActionResult>(Redirect(PostLogoutRedirectUri));
}

Share you backend logs please

We have added it to the patch and merged it. In the first release it will be fixed.

I have refunded your question, thank you for reporting.