Activities of "maliming"

hi

Try to inject IDistributedCache<PermissionGrantCacheItem> service.

Then remove the cache keys, the key is calculate by PermissionGrantCacheItem.CalculateCacheKey(name, providerName, providerKey);

Name is permission name providerName is U or R providerKey is UserId or RoleName

Thanks.

The login flow video: https://we.tl/t-cuDV5W00BK

hi

I did some changes to your XXXAuth and XXXCore

https://github.com/demirburak/.XXXAuth/pull/1 https://github.com/demirburak/.XXXCore/pull/1

XXXAuth is like a Google website.

XXXCore.HttpApi.Host is your AuthServer, and it supports XXXAuth/Google login

XXXCore.Web login flow is:

1. XXXCore.Web login => redirect to AuthServer(XXXCore.HttpApi.Host) login page.
2. Select XXXAuth/Google login in AuthServer(XXXCore.HttpApi.Host) login page.
3. Redirect to XXXAuth/Google website
4. Sign in with the account of XXXAuth/Google website
5. Redirect to AuthServer(XXXCore.HttpApi.Host) and it will create a new user, all user info coming from XXXAuth/Google website
6. Also singined in AuthServer(XXXCore.HttpApi.Host)
7. Redirect to XXXCore.Web

The user info in XXXCore.Web and AuthServer(XXXCore.HttpApi.Host) is the same user. And it exists in XXXCore database.

At the same time, the same user also exists in your XXXAuth/Google database.

If you want to auto-login by XXXAuth/Google account in the AuthServer(XXXCore.HttpApi.Host) login page. You can override the Login page OnGetAsync method and call:

public override async Task<IActionResult> OnGetAsync()
{
    return Challenge("oidc");
}

Thanks.

hi

I have downloaded ServerA and B solutions.

Can you share the steps to reproduce the exception?

Thanks.

hi

Thanks. Has your problem been solved?

hi

Can you confirm you changed the correct database and CodeAdvisor_App?

You can send an email to liming.ma@volosoft.com. I will share the Zoom link.

Thanks.

Thanks, I will check the code.

hi

It could be that there are minor changes in your server environment or code. Errors don't just appear out of nowhere.

Thanks.

Great 👍

hi

You can try to change ReferenceHandler in your project. But it will be best if we can reproduce it locally.

PostConfigure<AbpSystemTextJsonSerializerOptions>(options =>
{
    options.JsonSerializerOptions.ReferenceHandler = null;
});

Thanks.