Sign up flow missing information for Edit Profile

Which Version of MSAL are you using ?

2.7.1

Platform xamarin android

What authentication flow has the issue?

• Desktop / Mobile
  • Username Password

Is this a new or existing app? b. The app is in production, I haven’t upgraded MSAL, but started seeing this issue

Repro

var your = (code) => here;

Expected behavior A clear and concise description of what you expected to happen (or code).

authenticationResult = await ADB2CClient.AcquireTokenAsync(Scopes, firstAccount, UIBehavior.SelectAccount, string.Empty, null, AuthorityEditProfile, App.UiParent);

Actual behavior

Functionality works in that I can bind above to a button, however the page that is returned is hard for users to follow

1. It contains two fields which are for username and password, but without labels so you wouldn’t know
2. Further confused by an error message displayed within the email text box

Possible Solution

1. Label the text fields correct as Username / Email, and Password
2. Display the email address from the profile, not the error message

Additional context/ Logs / Screenshots Add any other context about the problem here, such as logs and screebshots. Logging is described at https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/wiki/logging

[DaveBrickley]

@jmprieur

FIXED

I’m really sorry, I read your samples and I finally figured it out from that, yes this totally sorts my problem, sorry for all the questions

[DaveBrickley]

@jmprieur

Depends, for a more experienced developer might be fine, for a relative newbie it was really confusing

Going right back to when I started using MSAL, I was firing off various tickets because I couldn’t access the B2C profile information from the token

This seemed really strange, because you’d have thought it was a primary use case

I ended up using MSAL in app and ADAL in API to work around this, passing the Object ID from the token to achieve what I needed

However, now looking through the additional link you’ve sent me to, I’m wondering if that whole issue could have been avoided had I noticed the authority change to use the b2c domain?

In terms of my latest problem, it might be nicer for people in this position in future if the ability to specifiy the B2C element as part of the main library, rather than having to write a method to do it?