title: MSAL and AD B2C issues with login
body: <p>I've invested some considerable time into trying to understand and properly use MSAL but I'm still struggling.  I have numerous issues and I'm not really sure what to do/what I'm doing wrong.</p>
  
  <p>Here's what I do have:</p>
  
  <p>1) The Active-Directory-B2C-Javascript-Angular2.4-spa application downloaded from github.</p>
  
  <p>2) I reconfigured it to use my B2C tenant I created</p>
  
  <p>3) I can login via Facebook or create my own account (sometimes)</p>
  
  <p>From here I'm struggling with two problems now: acquireTokenSilent - always fails, and ends up calling acquireTokenPopup (which appears to popup a window).  So I'm not sure why acquireTokenSilent is failing, but when it calls acquireTokenPopup the popup gets blocked.</p>
  
  <p>1) I'm thinking the acquireTokenSilent failure may be due to my "scope" i'm requesting.  I've looked through the Azure documentation and don't understand how to create a scope so I'm kind of stuck there.  Is there a default I can use?  I tried an empty string and it failed.  I also tried <a href="https://myapp.onmicrosoft.com/demoapi/demo.read" rel="nofollow noreferrer">https://myapp.onmicrosoft.com/demoapi/demo.read</a> which didn't make sense, but I tried it anyway (didn't make sense because I couldn't see it anywhere).</p>
  
  <p>2) I thought maybe removing my popup blocker which is defaulted in every browser now could maybe cause acquireTokenPopup to work.  INSTEAD:  It still fails, BUT when I call loginPopup it opens the login window twice.  Yes Twice.  I debugged the code to ensure I wasn't calling loginPopup twice.  I wasn't...</p>
  
  <p>Can somebody explain why in an age of popup blockers a library would even attempt this code?  Having somebody enable popups just to use your app seems incredibly archaic...  Is there a way around this with this library?</p>
  
  <p>Anyone have any advice?</p>