Please provide us with the following information:

This issue is for a: (mark with an x)

- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Click "Sign up with your work account"
Sign in on my organisation's sign in page

Any log messages given by the failure

Microsoft.IdentityModel.Protocols.OpenIdConnect.OpenIdConnectProtocolException: Message contains error: 'server_error', error_description: 'AADB2C90289: We encountered an error connecting to the identity provider. Please try again later.
Correlation ID: 63f8e242-6d6e-472a-8643-032c3a6cb318
Timestamp: 2019-10-02 14:51:03Z
', error_uri: 'error_uri is null'.
at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1.HandleRequestAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

Expected/desired behavior

I am able to sign up to the application

OS and Version?

Windows 10, Google Chrome or IE 11

Versions

Mention any other details that might be useful

Logged in response to MicrosoftDocs/azure-docs#39955

---

Thanks! We'll be in touch soon.

I searched for official documentation about the UserJourneyContextProvider used in this sample. I couldn't find any. I could not make it work in my custom policy (with no informations about why in ApplicationInsights of course). So I was wondering if this provider "Web.TPEngine.Providers.UserJourneyContextProvider" still exists and if so, is there any documentation out there about how it works?

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Versions

Mention any other details that might be useful

Hi, I'm trying to setup Azure B2C with the requirement that I want to collect additional user data on subsequent logins. I've see this demoed here: https://youtu.be/GmBKlXED9Ug?t=433 and wondered if this demo has it also? I can't find any reference to it in this repo. Any help regarding how to get started with the progressive profiling feature will be much appreciated.

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [X ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Attempted to launch URL https://woodgrovegroceriesb2c.azurewebsites.net/; page wouldn't load.

Any log messages given by the failure

I reach this message on the page: Hey, App Service developers!

Your app service is up and running.
Time to take the next step and deploy your code.

Expected/desired behavior

I can see a log in page.

OS and Version?

Windows 10

Versions

1809

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Visit https://woodgrovegroceriesb2cdemo.azurewebsites.net/

Any log messages given by the failure

n/a

Expected/desired behavior

Master branch source code aligned with the code deployed at woodgrovegroceriesb2cdemo.azurewebsites.net

OS and Version?

n/a

Versions

master branch source code

Mention any other details that might be useful

Hi, the current woodgrove grocery sample deployed at woodgrovegroceriesb2cdemo.azurewebsites.net doesn't seem to be exactly the same code within the master branch of this repo. For example the live version has a Configuration endpoint that seems to be missing here. Is this the correct repo for the application? Thanks.

---

Thanks! We'll be in touch soon.

This issue is for a: (mark with an x)

- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

• visit https://woodgrovegroceriesb2c.azurewebsites.net/Account/LogIn
• click on Sign in with your personal account using an A/B policy (preview)

Any log messages given by the failure

Expected/desired behavior

No error

Look like the code is not using any Azure AD Client Libraries (MSAL) , instead its using Open ID urls and AuthenticationBuilder for asp.net core for all auth related configuration and execution.

Any specific reason why not using the Azure AD client libraries for this demo app ? Looking for developer guidance , pros / cons on choosing this method. Thank you !

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [X] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

• visit page

Any log messages given by the failure

none

Expected/desired behavior

no redundant labels for email and password

Angular Material Design Example

Looks really good btw!! 👍👍

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

When you open de 'Forgot your password' screen on https://woodgroveb2cdemo.azurewebsites.net/ and fill-in your email address you can then press the 'SEND VERIFICATION CODE' button to request a verification code. But many users wil use the 'go' button on the virtual keyboard because they are allready typing.
The behaviour is different on IOS and Android.
On IOS you will be redirected to the login screen and no code is send. Thats not what the user expect
On android nothing happens. No code is send. this is also not what the user expect

Any log messages given by the failure

Expected/desired behavior

Pressing the 'go' button on the virtual keyboard should have the same behaviour as pressing the 'SEND VIRIFICATION CODE' button

OS and Version?

IOS 13.6 and Android 9

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [ X] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Mention any other details that might be useful

I would like to build a working verision of this demo in my environment. Could you provide some documentation on what is required. The whitepaper is vague and doesn't include specifics based on the code provided.

---

Thanks! We'll be in touch soon.