title: IN.User.Authorize callback never fired
body: <p>Since today, our application that uses the linkedin javascript SDK to authenticate users stopped working.
  ​
  We realized that the call to <a href="https://platform.linkedin.com/in.js" rel="nofollow noreferrer">https://platform.linkedin.com/in.js</a> now redirects to  <a href="https://platform.linkedin.com/xdoor/scripts/in.js" rel="nofollow noreferrer">https://platform.linkedin.com/xdoor/scripts/in.js</a>.</p>
  
  <p>​
  Consequently, calls to <code>IN.User.Authorize(callbackFunction)</code> successfully opens the authentication dialog window but the callback is never fired anymore.
  ​</p>
  
  <p>Also, in another part of our application we are using the <code>IN.UI.Authorize.place().onWindowRemove.subscribe(callbackFunction)</code> to track dialog closes. This feature has also stopped wording and now opens a new window with the url <code>invalid://</code> and the console throws this error:
  ​</p>
  
  <pre><code>jSecure Error: URL should be absolute with allowed schemas, relative, a hash fragment or query string. TODO?client_id=XXXX&amp;amp;type=user-agent in.js:7
  ​
  jSecure Error: URL should be absolute with allowed schemas, relative, a hash fragment or query string. invalid://?xdOrigin=https%3A%2F%2FXXX-XXX&amp;amp;xdChannel=XXXX&amp;amp;xd_origin_host=https%3A%2F%2FXXXX.XXXX in.js:7 
  ​
  jSecure Error: URL should be absolute with allowed schemas, relative, a hash fragment or query string. TODO?client_id=XXXX&amp;amp;type=user-agent
  </code></pre>
  
  <p>​
  ​
  Do you have an idea on why this stopped working ?</p>
  
  <p>EDIT: Bug reappeared as of 2019 01 28.</p>