Known Issues and Workarounds

This page covers known issues that exist outside of MSAL4J, such as those found in dependencies or services that MSAL4J relies on, and potential workarounds to use until those issues are resolved.

B2C

Missing access token when using B2C

Cause: There is an assumption in MSAL4J that the authorization server will always return an access token in a response to a valid request, as per the OpenID Connect and OAuth 2.0 specs. However this assumption leads to an exception in MSAL4J in certain B2C flow scenarios, because the B2C service only returns an access token if custom scopes are included the request.

Workaround: Until this issue is resolved on the B2C side, you can avoid an exception in MSAL4J by including a custom scope in the token request. The B2C docs recommend using the client ID of the application as the scope.

See this issue for more information.