Azure B2C Implicit Flow for SPA using Auth API gives invalid token for openid scope
<p>I have setup my application to use Azure B2C's Implicit Flow token strategy to give me tokens via the post-signup/signin login in the URI. This works fine and the tokens authorize without a hitch.</p>

<p>However, the client is an SPA, so when the token expires, the documented workaround suggested by Microsoft is to use an iframe that makes a call to the <code>authorize</code> endpoint as documented here: <a href="https://docs.microsoft.com/en-us/azure/active-directory/active-directory-v2-protocols-implicit#get-access-tokens" rel="nofollow noreferrer">Get Access Tokens</a></p>

<pre><code>https://login.microsoftonline.com/{tenant}/oauth2/v2.0/authorize?client_id={my_client_id}&amp;response_type=token&amp;redirect_uri=http%3A%2F%2Flocalhost%2Fmyapp%2F&amp;scope=openid&amp;response_mode=fragment&amp;state=12345&amp;nonce=678910&amp;prompt=none&amp;domain_hint=organizations&amp;login_hint=myuser@mycompany.com
</code></pre>

<p>Unfortunately if I request an id_token using the openid scope with this endpoint, the token that's actually returned does not authorize via B2C in my API. Examining the JWT token in a decoder also shows that the token itself looks different than the one given post-signin from B2C.</p>

<p>I realize this documentation is for Azure Active Directory and that <a href="https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-apps#current-limitations" rel="nofollow noreferrer">B2C doesn't support SPAs at this point</a>, but I had heard from Microsoft representatives previously that this should work. </p>

<p>Is this really not supported yet? And if not, are there any workarounds for SPAs?</p>