[Feature Request] Remove requirement for including /tfp/ for B2C

Is your feature request related to a problem? Please describe. If you are using B2C, you have to pass in this authority: https://{tenantName}.b2clogin.com/tfp/{tenant}/{policyName}

Most B2C users do not use /tfp/ anywhere in their code, so it doesn’t make sense to require it for MSAL libraries as part of the authority. Leads to confusion.

Describe the solution you’d like Braindump:

• Remove .WithB2CAuthority and use introduce .WithAuthority(string authority, string trustFrameworkPolicy), which would look like this:

.WithAuthority("https://catsCity.b2clogin.com", "b2c_sisu") All B2C policies (including custom) are prefixed w/b2c. We’d have to have the policy included to know what to target.

• Revisit previous proposal:

.WithB2CAuthority("https://catsCity.b2clogin.com")

.WithTrustFrameworkPolicy("b2c_sisu")

• .WithB2CAuthority(https://{tenantName}.b2clogin.com/{tenant}/{policyName})

• .WithAuthority(https://{tenantName}.b2clogin.com/{tenant}/{policyName}) and look for b2c in the policy to determine it’s b2c

• In the case of custom domains, the domain name and the tenant name might be different, so require this as the authority for b2c: .WithAuthority("https://cats.com/petsUnlimited.onmicrosoft.com", "b2c_sisu")

Additional context We have to know the authority and the policy for b2c. So any proposals must include those two parameters.

[jmprieur]

ok @jennyf19. I thought that I created it as an outcome of the group. But maybe not. I don’t remember. Closing it, then.

[jennyf19]

@henrik-me You’re referring to TrustFrameworkPolicy? I’m not sure, but can find out.