This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(278.4, 85%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGS%3C/text%3E%3C/svg%3E)
Thank you very much in advance.
I want to implement a SignIn/Login page (in my site not in Azure) in a Blazor Server App that connects with a .Net Core API which in turn connects with an Azure Active Directory B2C.
The Blazor App should send the credentials (email and password) to a .Net Core Api and this one should send the credentials to Azure Active Directory and this one should sign in the user and return a token with the claims.
I'm a little bit lost because there are a lot of different Microsoft Learn with similar topics but I'm not really sure which blog/doc is the right one for my use case, it would be really great if someone pointed me in the right direction.
Thank you again.
You would have to Configure the resource owner password credentials flow in Azure AD B2C for your API.
--
Please let us know if this answer was helpful to you. If so, please remember to mark it as the answer so that others in the community with similar questions can more easily find a solution.
There are some notes of Microsoft not recomending ROPC unless necessary and also it's currently on Preview.
Someone else mentioned this samples https://github.com/Azure-Samples/active-directory-aspnetcore-webapp-openidconnect-v2.
Which is the difference between the Resource owner password credentials flow (ROPC) and the samples mentioned? Is there any of those samples that would better than ROPC for my use case? Also Microsoft mentions as an alternative MSAL.NET is this also a valid option for my use case?
Is true ROPC is not recommend but its the only one that fits your architecture. The mentioned samples use other flows such as Authorization Code, etc. And yes you can/should use MSAL.NET
--
Please let us know if this answer was helpful to you. If so, please remember to mark it as the answer so that others in the community with similar questions can more easily find a solution.