Activities of "duyan11110"

Hi,

So, when dynamic claim is called? Every 1 hour?

Hi,

I fixed this issue by adding this code in WebModule to change Dynamic Claim URL for internal call in K8s

context.Services.Configure<AbpClaimsPrincipalFactoryOptions>(options =>
{
    options.IsDynamicClaimsEnabled = true;
    options.RemoteRefreshUrl = configuration["AuthServer:MetadataAddress"] + options.RemoteRefreshUrl.Replace(configuration["AuthServer:Authority"],""); --> ADDED THIS LINE
});

But can you explain why dynamic claim impact to Access Token lifetime?

Hi,

Already sent identitymodel.txt. Please check.

Hi,

Please check the logs I've sent to your email. After 1 hour, I access to another page and see this in Web log:

[10:13:25 INF] Sending HTTP request POST https://authserver.upgrade-staging.mizuho.vn/api/account/dynamic-claims/refresh

and K8s can not understand the domain (it should be http://authserver-upgrade-staging/api/account/dynamic-claims/refresh for internal call). In localhost, access token is still valid more than 1 hour

Hi,

I've sent the logs. Please check.

I don't set token lifetime for each Application. Only set this one in AuthServerModule. It will affect for all Application, right?

PreConfigure<OpenIddictServerBuilder>(builder =>
{
    builder.SetAccessTokenLifetime(TimeSpan.FromHours(24));
});

I've sent you access token via email

As you can see exp is 24hours, but still unauthorized after 1 hour

Hi,

So, did you already fix the issue of increasing Access Token liftetime in v9.1.3?

Hi,

What is the reason of that issue? I just want to fix only that issue firsrt, because it is on Production. Upgrade to new version will take much time.

Hi,

Is there any specific code that I can change? Because I've just upgraded to v9.1.0 and released on Production, upgrade to new version need to be tested carefully

Hi,

Already sent. Please help to check.