You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current ASP.NET Core guidance in the Graph docs (along with the weather data guidance) indirectly address how Graph would be added to a BWA with Interactive Auto/WASM rendering. Similar to what we did for Graph+Blazor WASM, it would be quicker and easier for devs to implement Graph if we show them how to do it in our docs. Forwarding devs to the Graph docs is going to be too challenging for new devs and new-to-Blazor devs and will end in tears 😢 for many ... and issues for us 💰.
UPDATE: Given that the current section on app roles with ME-ID looks like it may lead to cookie/header length problems, let's place Graph SDK/API for AD groups and AD built-in Admin Roles ... and let that be the example of using Graph.
UPDATE: Actually, I suppose the current section would be fine if users only have a couple of AD groups/roles. Perhaps, there should be a remark to that effect for the existing section ... and then there should be a new section for Graph SDK/API for AD groups/roles. Then, devs can decide which approach makes the most sense for an organization. Still tho, I think we'd favor telling devs to adopt the Graph SDK/API to harden the app for the future. 🤔 ... I'll think it over next week.
RE-closing because I could only get the REST API to play nicely with the BWA+OIDC app. We won't cover it beyond passing the claims in the auth cookie at this time.
Description
Current ASP.NET Core guidance in the Graph docs (along with the weather data guidance) indirectly address how Graph would be added to a BWA with Interactive Auto/WASM rendering. Similar to what we did for Graph+Blazor WASM, it would be quicker and easier for devs to implement Graph if we show them how to do it in our docs. Forwarding devs to the Graph docs is going to be too challenging for new devs and new-to-Blazor devs and will end in tears 😢 for many ... and issues for us 💰.
UPDATE: Given that the current section on app roles with ME-ID looks like it may lead to cookie/header length problems, let's place Graph SDK/API for AD groups and AD built-in Admin Roles ... and let that be the example of using Graph.
UPDATE: Actually, I suppose the current section would be fine if users only have a couple of AD groups/roles. Perhaps, there should be a remark to that effect for the existing section ... and then there should be a new section for Graph SDK/API for AD groups/roles. Then, devs can decide which approach makes the most sense for an organization. Still tho, I think we'd favor telling devs to adopt the Graph SDK/API to harden the app for the future. 🤔 ... I'll think it over next week.
Working this will now solve #33450.
Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/security/blazor-web-app-with-oidc?view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/security/blazor-web-app-with-oidc.md
Document ID
c3346d3a-346b-8db4-2650-ec044b3f0dd9
Article author
@guardrex
The text was updated successfully, but these errors were encountered: