Show how to execute additional policies once the user is already logged in about active-directory-b2c-dotnetcore-webapp

[dstrockis]

Looks like this workaround is to be fixed/removed in a future version of the middleware: aspnet/Security#980

[Bigshooter]

@dstrockis I attempted your fix and I no longer receive the Forbidden message, however I now get https://websiteURL/B2C_1_policysigninsignup .... any direction would be a great help.

[Bigshooter]

Took some time but I figured it out. I did not add my dev redirect URL for editing a profile to azure B2C redirect URLS.

[gsacavdm]

@dstrockis even after updating to 1.1 this still seems to be necessary.
See #15

Is the expectation that we should not need the ChallengeBehavoir?

[danroth27]

@Tratcher @HaoK

[nhwilly]

It looks like you all are working on this really neat capability. It would great if someone could author a blog post on how to do it correctly. I've chased my tail for days and I can't get the behavior I want. Mostly because I'm not entirely sure I know what's going on under the covers. Thanks...

[jmprieur]

Closing this issue as this sample is being archived and replaced by a newer ASP.NET Core 3.1 sample.
See Readme.md