Skip to main content

Adding Entra ID Auth to a Blazor App

I wanted to take the time to write up this article since I found it useful when working on Blazor Apps. Althought this is not Sitecore related, I think it will be useful if we need to build an admin .NET portal. Additionally most organizations already have Entra ID if they use Microsoft apps and building Entra ID Authentication wont add costs like other Authentication methods would.
To get started make sure the following packages are available (using NuGet) in your solution.



In your Program.cs file, add the following


In my example, I am going to put my entire application behind the Authentication, except the home page. So users cannot get to any page in the application un-authenticated except the home page.

In your App.razor file, add the following (surround your existing Routes with CascadingAuthenticationState)


In your Home.razor file, add the following


Add a new Login.razor file with the following content


Lastly in your appsettings.json file add the following (or add this in your environmental variables for production apps)


Note:
You get the TenantId and ClientId by going to your Azure Portal Microsoft Entra ID and registering a new App. Once you register a new app you would note down the ClientId and use it in your application And lastly to test this out, make sure that you have the right redirect urls added to the list of "Redirect URI's." for the new app that you created. This is found by going to the Authentication section of your new App in your Azure portal. For example the following are ones that are common.



That's it. Simple way to add secure Entra ID Authentication to your Blazor App.

Comments

Popular posts from this blog

Back-End and Front-End Development in Sitecore XM Cloud

  Understanding the Roles In Sitecore XM Cloud, back-end developers primarily manage content models, custom APIs, and data within the Sitecore CMS backend. On the other hand, front-end developers focus on building the user interface and interactions using a JavaScript framework like React, consuming content from the backend via GraphQL endpoints. The headless CMS architecture of Sitecore XM Cloud allows the front-end to be largely decoupled from the back-end, providing flexibility in technology choices and development workflows. Back-End Developer Responsibilities Back-end developers in Sitecore XM Cloud are responsible for: Deployment of all custom components to XM Cloud. Synchronizing components, code, and content between Prod and Non-Prod environments. Answering questions from content authors regarding component usage, troubleshooting site load, caching, and component versions. Troubleshooting Edge CDN issues related to content updates. Designing and managing content structures,...

Sitecore XM Cloud local development setup

Below are my notes when setting up a local Sitecore XM Cloud development environment. There are many good blog articles for local XM setup but the following 3 were the most useful for me Blog 1 - Used for Docker setup Blog 2 - Used for Rendering site setup Blog 3 - Used to install test content in local CM Using the information from the first 2 articles I was able to setup my local docker environment by running the up.ps1 script and then having a local Sitecore instance running on https://xmcloudcm.localhost I also had my local next js rendering site running using start:connected and accessed using the url http://localhost:3000 You can write all your rendering React code in your React app. You can create components using Json renderings in Sitecore and have corresponding tsx files in the components folder of your React app. For any Sitecore content items that are part of the component, you serialize those items as yml files in your codebase. ...