This is an awesome introduction to Azure auth. Thanks for sharing your steps, pains and hoops we need to jump through, hopefully you'll get chance to follow-up with the Claims and Scopes parts.
Thank you both for such perfectly paced, well explained information. Azure portal is uber confusing and it's so easy to lose the setting you were looking at 2 minutes ago - this really helped to clarify things for me...thank you.
This was fantastic and allowed me to get my B2C up and running and auth working with my Blazor App. But now I have an issue where my signalr hubs are all failing. Before I used basic cookie auth and I guess the cookie is automatically passed through. So how about a video of signalr with auth? Hmmmm, yeah that sounds nice.
Great video. This answered a ton of questions. My only challenge getting the published app to work. It works under localhost, but not after I publish. Simple get "hmmm... cannot connect to localhost."
Carl, the text file you provided, is for Blazor Server and startup.cs with stuff in it that doesn't have anything to do with Blazor Wasm. Could you please, create a text file for Blazor Wasm? Thanks!
Can you please provide some info about the log out process as well? How can we redirect users to sign in/ sign up view of Azure AD B2C when they click on log out link/button?
Thanks, very useful, was wondering how to add B2C on Blazor Server, now we have it working, however when azure b2c redirects to “/signin-oidc” it is not found, it is not even caught by the App’s router at all. Checked the links and all are correct
Thanks for the clear and detailed explanation. One question (not strictly a B2C question)... Your example app requires authentication prior to accessing any part of the Blazor app. Is there a way to allow anonymous access to a Home page, for example, with the option to authenticate for full access to other pages? How does the configuration "plumbing" have to change in the Blazor app?
options.FallbackPolicy = options.DefaultPolicy; is causing that. You need to make a policy, something like: var policy = new AuthorizationPolicyBuilder().RequireAuthenticatedUser().Build(); options.AddPolicy("mypolicy", policy); and then use @attribute [Authorize] on your pages you want to secure.
Great video! Is there any way to just show a login link at top right on menu instead of going straight to the login screen? I would like users to have to click the link to optionally log in? Thanks!
Hi guys - thanks for this video! I followed your steps exactly, however the links you got us to add in the LoginDisplay component dont actually work ie "MicrosoftIdentity/Account/SignIn" as they dont exist. Did you guys forget a step by any chance?
Thanks for yet another great tutorial. I implemented this in my application and I can now Sign in/up. But the 'Forgot password' link on the sign in page doesn't work. Did you already implemented it and are you willing to share that part. As I understand some additional coding needs to be done to get it working.
I REALLY apricate the subject and depth you are going in these videos. This level has been hard to find and much needed. Please stop zooming in to things. It is much more difficult to read when the screen moves in and out and around. We can read the stuff happening just fine without the zooming.
This is an awesome introduction to Azure auth.
Thanks for sharing your steps, pains and hoops we need to jump through, hopefully you'll get chance to follow-up with the Claims and Scopes parts.
Wow, great job guys! Slow and steady, actually teaching how to make it work!
Thank you both for such perfectly paced, well explained information. Azure portal is uber confusing and it's so easy to lose the setting you were looking at 2 minutes ago - this really helped to clarify things for me...thank you.
Glad it was helpful!
+1 for Multi-Tenancy
Thanks for tutorial on the new libraries! Microsoft really leaves us hanging on simple things like logout page...
This was fantastic and allowed me to get my B2C up and running and auth working with my Blazor App. But now I have an issue where my signalr hubs are all failing. Before I used basic cookie auth and I guess the cookie is automatically passed through. So how about a video of signalr with auth? Hmmmm, yeah that sounds nice.
Carl. Can we have a video for integrating OIDC with Blazor WASM standalone?
Great video. This answered a ton of questions. My only challenge getting the published app to work. It works under localhost, but not after I publish. Simple get "hmmm... cannot connect to localhost."
Carl, the text file you provided, is for Blazor Server and startup.cs with stuff in it that doesn't have anything to do with Blazor Wasm.
Could you please, create a text file for Blazor Wasm?
Thanks!
Can you please provide some info about the log out process as well? How can we redirect users to sign in/ sign up view of Azure AD B2C when they click on log out link/button?
Thanks alot for this tutorial. I am struggling however with the redirect after logging out, do you perhaps have any tips?
I am struggling with it now, too. Is there any solution to this?
Hi I'm struggling with the same. Any help is appreciable.
Thanks, very useful, was wondering how to add B2C on Blazor Server, now we have it working, however when azure b2c redirects to “/signin-oidc” it is not found, it is not even caught by the App’s router at all. Checked the links and all are correct
Thanks for the great video. The way it handles redirect uris is very confusing I must admit. At least I now know where to point my own research.
You are welcome!
Looking forward to role based access with B2c & Blazor PWA + Azure AD B2c token/session management
Thanks for the clear and detailed explanation. One question (not strictly a B2C question)... Your example app requires authentication prior to accessing any part of the Blazor app. Is there a way to allow anonymous access to a Home page, for example, with the option to authenticate for full access to other pages? How does the configuration "plumbing" have to change in the Blazor app?
Yes there is way to allow anonymous access
options.FallbackPolicy = options.DefaultPolicy; is causing that. You need to make a policy, something like: var policy = new AuthorizationPolicyBuilder().RequireAuthenticatedUser().Build(); options.AddPolicy("mypolicy", policy); and then use @attribute [Authorize] on your pages you want to secure.
Amazing guys , b2c and Microsoft.indentity.web for API seems to be the future for quick app Auth
Great video! Is there any way to just show a login link at top right on menu instead of going straight to the login screen? I would like users to have to click the link to optionally log in? Thanks!
Can we do this for blazor hybrid?
Hi guys - thanks for this video! I followed your steps exactly, however the links you got us to add in the LoginDisplay component dont actually work ie "MicrosoftIdentity/Account/SignIn" as they dont exist. Did you guys forget a step by any chance?
Sorry just realised I missed that one step in your video!
I can't even install those 4 packages in a Blazor WASM app. This is for Blazor Server only, I guess.
Thanks for yet another great tutorial. I implemented this in my application and I can now Sign in/up. But the 'Forgot password' link on the sign in page doesn't work. Did you already implemented it and are you willing to share that part.
As I understand some additional coding needs to be done to get it working.
Look up "Add new Scaffolded Item" Choose Identity. You get a whole list of items you can implement including "Forgot Password"
I am not being flippant when I ask, "In App.cs can you wrap a CascadingApplicationState in a CascadingAuthenticationState? "
Hi Nicholas, Thanks for the question. The answer is Yes, you can.
Great stuff! What's the "add some more code" needed to extract more items from the JWT other than the .Name?
I REALLY apricate the subject and depth you are going in these videos. This level has been hard to find and much needed.
Please stop zooming in to things. It is much more difficult to read when the screen moves in and out and around. We can read the stuff happening just fine without the zooming.
my app does start after I add app.UseAuthorization()