Activities of "maliming"

hi

If you have gotten and set the ProductToken, you can downgrade the Blazor to 1.8.1. I will confirm this with the Blazorise team

Thanks.

services.AddBlazorise( options =>
{
    options.ProductToken = "<your-product-token>";
})

https://abp.io/support/questions/5037/How-do-we-get-support-with-Blazorise#answer-3a0b3114-427d-f26e-4cc5-88ff791f3ff3

hi

2.) The login page comes from the Account module. How can I customize it? I would appreciate a link explaining this section. Because I created Pages/Account/Login.cshtml in the Host layer and added the relevant code to the OnGetAsync method. Since it was redirecting incorrectly, I deleted it all and reverted it.

I pushed new code.

see https://github.com/demirburak/xxx/pull/1/commits/9d38ecac1b024f2f34c3dc1f39c1090d3190e265

hi

1.) The sign-up button is inactive. Actually, is there a parameter for automatic registration, as if this button didn't exist? In other words, if identity verification is successful, can it automatically register locally?

Please try to run abp install-libs command in your XXXCore.HttpApi.Host project. And re-run the app.

这个RequestClientCredentialsTokenAsync方法来自 IdentityModel 类库

https://docs.duendesoftware.com/identityserver/tokens/requesting/#net-client-library

如果第三方是net 应用程序可以直接引用并使用它获取token并消费API.

是的, RequestClientCredentialsTokenAsync 也是POST请求

请参考 https://github.com/abpframework/abp/blob/dev/modules/openiddict/app/OpenIddict.Demo.Client.Console/Program.cs#L165-L195

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.