Inspiration

Blazor UI as a Razor Component Library within a web API which uses Graph API and authenticates against AAD B2C.

What it does

Manages AAD B2C users.

How I built it

I started from Graph API calls to create/edit a user. I made these part of a web API project and then built a UI to consume them. I then made the UI part of the web API as a RCL.

Challenges I ran into

Some issues with app settings not being updated correctly on the app service once deployed, but totally my fault :).

Accomplishments that I'm proud of

Blazor UI within web API is great. Reusable UI. Integration with Graph API is very nice. What you can do with it is amazing. This is a user friendly tool for managing B2C users with the potential to grow and manage other parts of AAD B2C.

What I've learned

How to integrate a modern web app that calls a web API and Graph with AAD B2C.

What's next for AAD B2C User Admin

Implement a signed user invite via id token hint and a custom policy for sign-up from invite. Implement pagination for the users list. Integrate more AAD B2C features, such as Application management. Implement RBAC for users on the basis of a data store. (i.e. create user groups and associate them to applications.) Expose an API endpoint that can be called by the B2C policies to retrieve group memberships). Provide a smart UI for handling custom B2C policy localisations. etc...

Built With

  • .net6
  • aad-b2c
  • blazor
  • c#
  • web-api
Share this project:

Updates