Documentation Does Not Match Current Azure Portal UI about active-directory-aspnetcore-webapp-openidconnect-v2 HOT 9 CLOSED

@markolbert
I'm sorry for your frustration with our samples. I can assure you that we spend a lot of time updating them.
That said, I'm confused as for me the description above maps to the experience in the portal.

Then given that a URL is a kind of URI, I had not thought that "adding a redirect URL" would be wrong (especially the text below the Redirect URIs heading explains that reply URLs and redirect URLs are the same thing.).

Are you seing something different? Or otherwise what am I missing?

from active-directory-aspnetcore-webapp-openidconnect-v2.

Yep, I'm seeing something totally different. Here's what I thought was the top-level view:

This is inside my tenant directory.

When I click on the newly-created/registered app, here's what shows up:

How did you navigate to what you're seeing? Did I create/register an app in another part of the Azure Portal unrelated to what the documentation assumes?

from active-directory-aspnetcore-webapp-openidconnect-v2.

@markolbert
I've 2 questions for you:

• In which Azure region are you?
• When you click on Azure Active Directory in the vertical menu bar on the left-hand side, don't you see App Registration (Preview) ?

cc: @lnalepa FYI.

from active-directory-aspnetcore-webapp-openidconnect-v2.

@markolbert Unfortunately, the preview experience is currently not available in B2C tenants. Are you able to use another tenant? I have answered your StackOverflow question.

from active-directory-aspnetcore-webapp-openidconnect-v2.

Nope. I don't see a preview, just App Registrations (I assumed it had been released, and was no longer in preview):

I noticed that @lnalepa has just added to this thread that the preview experience is not available in B2C tenants. Any idea on when it might be available? Or if there's a workaround for it not being available yet?

FWIW, it'd be worth putting a noticeable disclaimer in the sample docs that they don't currently work with B2C tenants. That's probably obvious to people who know what they're doing. But for those of us who are trying to learn this stuff, it's not clear why an example which sure seems like it ought to apply, doesn't.

I will also point out that this situation is an example, IMHO, of what happens when a software environment is rapidly evolving (and here I'm not talking about the Azure Portal, but the broader Azure Active Directory environment). Stuff gets "disconnected" from the current state of the art. What's worse, because all the documentation -- both current and older stuff -- comes up through online searches, it becomes extremely difficult, for newcomers and/or people who don't live and breathe a particular subsystem, to separate the wheat from the chaff.

I'm not sure how to do it, but there needs to be a much stricter curating function for the documentation. Right now all I can do is check the date stamp on when the documentation last got published, and discount anything more than X months old...which is a really silly way of trying to substitute for a curating process.

from active-directory-aspnetcore-webapp-openidconnect-v2.

@markolbert i'm from the Azure AD B2C product team. Are you trying to register a B2C application to authenticate using Azure AD B2C? If so, you should be using the app registration experience through the Azure AD B2C menu

See instructions here:
https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-app-registration

Screenshot here:

from active-directory-aspnetcore-webapp-openidconnect-v2.

Hi @parakhj. Here's what I'm trying to do: I want to authenticate users via social logins (currently Google & MicrosoftAccount), and then use Graph to store certain optional user information (those additional elements are optional because they define whether a user is a member of the site I'm building -- non-members get to use certain features of the site, but members get to use everything).

I explained this a bit more over on stackoverflow, at https://stackoverflow.com/questions/53603535/authentication-vs-authorization/53606885. I'm trying to follow the suggestion that was supplied there, which is why I stumbled into this sample.

from active-directory-aspnetcore-webapp-openidconnect-v2.

Closing this issue, as we've added a disclaimer that this sample is not for Azure AD B2C.
Thanks for the heads-up, @markolbert

See also #16 which is about providing a variation for Azure AD B2C

from active-directory-aspnetcore-webapp-openidconnect-v2.

@markolbert you should follow the instructions as outlined in https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-devquickstarts-graph-dotnet (the same doc that Abhishek linked to)

from active-directory-aspnetcore-webapp-openidconnect-v2.