in the current sample, if a developer updates just the CLIENT_ID in app_config.py (after renaming it from app_config_b2c.py, of course), several errors occur when navigating to the application and attempting to sign in, and the experience is busted.
That is because our placeholder B2C api scopes mismatch the actual scopes the customer has setup.
This is a short term workaround for #29, by not attempting to require consent for non-exist scopes during initial login.
Quoted from #29:
That is because our placeholder B2C api scopes mismatch the actual scopes the customer has setup.
This is a short term workaround for #29, by not attempting to require consent for non-exist scopes during initial login.