Activities of "liangshiwei"

Let me explain more.

To get access_token, Blazor WebAssembly and Blazor Server are different.

In Blazor WebAssembly

[Inject]
protected IAccessTokenProvider AccessTokenProvider { get; set; }

var token = await AccessTokenProvider.RequestAccessToken();

In Blazor Server

[Inject]
protected IHttpContextAccessor HttpContextAccessor { get; set; }

var token = HttpContextAccessor.HttpContext.GetTokenAsync("access_token");

Hi,

The details may be different when writing UI code, so ABP has created separate projects for them.

I think I have explained the difference well.

There is no documentation on what this project is and what it should be used for.

It should be easy to understand. Use .Blazor.WebAssembly if your project is Blazor WebAssembly UI Use .Blazor.Server if your project is Blazor Server UI

It happens because the issuer is automatically set by the request. you can try:

PreConfigure<OpenIddictServerBuilder>(builder =>
{
    builder.AddSigningCertificate(GetSigningCertificate(hostingEnvironment, configuration));
    builder.AddEncryptionCertificate(GetSigningCertificate(hostingEnvironment, configuration));
    builder.SetIssuer(new Uri(configuration["AuthServer:Authority"]!));
    builder.Configure(c =>
    {
        c.TokenValidationParameters.ValidIssuers = new List<string>()
        {
            configuration["AuthServer:Authority"]!,
            "https://app-scm-auth-test-qa-001.ase-sharedeawgeacbyumuk-qa-001.appserviceenvironment.net/"
        };
    });
});

It seems like struct's are not correctly processed when generating the api-definition.

It looks like this. I will investigate it.

Hi,

Is this document helpful to you? https://docs.abp.io/en/abp/latest/CLI#options-6

I think this is the same with question Can we close this and discuss in 5781?

OK, please share all the logs. let's try to check it.

Bearer was not authenticated. Failure message: IDX10205: Issuer validation failed. Issuer: 'https://auth.scm-test.lw.app/'. Did not match: validationParameters.ValidIssuer: 'null' or validationParameters.ValidIssuers: 'https://app-scm-auth-test-qa-001.ase-sharedeawgeacbyumuk-qa-001.appserviceenvironment.net/' or validationParameters.ConfigurationManager.CurrentConfiguration.Issuer: 'Null'

I think this may be related to your environment configuration

You can check this: https://support.abp.io/QA/Questions/3312/I-am-getting-redirected-back-to-the-login-page-after-a-successful-login#answer-6494c158-4516-8e1d-b79d-3a04a75ad57c

Hi,

Are there built in solution for this request?

You may consider setting cookies to the common domain. see: https://learn.microsoft.com/en-us/aspnet/core/security/cookie-sharing?view=aspnetcore-8.0#share-cookies-across-subdomains

Ahh thank you, that might be something I can work with. Coworkers of mine are actually right in the middle of upgrading to version 7.4 which I expect to be finished any time soon!

Ok, But there's a bug in Hangfire and fixed today, we haven't released the patch version:https://github.com/abpframework/abp/issues/18477 Your worker may execute twice(Only workers inherited from BackgroundWorkerBase)

You can avoid it in the following way:

public class MyWorker : BackgroundWorkerBase
{
    private bool IsRunning { get; set; }
    public override Task StartAsync(CancellationToken cancellationToken = default)
    {
        if(IsRunning)
        {
           return...
        }
        
        IsRunning = true;
        //...
    }

    public override Task StopAsync(CancellationToken cancellationToken = default)
    {
        //...
    }
}

Still pretty strange to me that the BackgroundWorker doesn't run and the PeriodicBackgroundWorkerBase does run in our current situation. If you can shed any light on this, that would be great!

Because Hangfire did not support BackgroundWorkerBase before, It will be ignored instead of added to the worker list.