Activities of "maazq"

How does ABP authencate a user when a user successfully login or signup in B2C?

It is default Microsoft Identity library behavior when you sign in from an external resource; AbpUser will be saved without password and AbpUserLogin will be saved with the login provider and provider key.

What I'm gonna make is want to add both authentications, ABP default login functionality also AD B2C login as external login.

My project backend is on ABP API and UI is on Angular. This article is one Azure Active Directory, I need help on Azure AD B2C.

You can check How to Setup Azure Active Directory and Integrate ABP Angular Application article.

This article is very helpful, I can authenticate users with Azure AD B2C. When I go login on AD B2C for the first time, it works fine but when I go login back on AD B2C, that throws the error. (Error image is attached below)

You can check How to Setup Azure Active Directory and Integrate ABP Angular Application article.

That article helped to configure Azure Active Directory but this is not for Azure AD B2C. My app successfully redirected to "https://login.microsoftonline.com/"(instance) and authenticated with Azure AD but when I configure Azure AD B2C, want it to go to "https://****ad.b2clogin.com/"(instance) to authenticate, it throws the error.

https://docs.microsoft.com/en-us/azure/active-directory-b2c/overview This is something I am trying to add into my angular app.

I have an ABP Angular application whose backend is on ABP asp .net core(API).

I want to enable Google, Facebook, and Microsoft authentication on my Angular application.

I am running command abp generate-proxy and abp generate-proxy --module app but nothing works.

Anyone from ABP support can answer my question?

For csharp static proxy: abp generate-proxy --type csharp --module yourModuleName --url https://moduleHost:modulePort

For javascript static proxy: abp generate-proxy --type js --module yourModuleName --url https://moduleHost:modulePort

Your module must be running while you are generating the proxies.

That worked, thanks.

When trying to login with Azure AD B2C getting this error, does not redirect to Azure AD B2C Login page.