The root causes are documented here #2238(summary version) and #600.
If using ui-router: Most common cause of running into infinite loops when using ui-router is state transition error. There could be multiple reasons for the infinite loop. My app gets into an infinite loop, sometimes leading to digest iterations error. If your app is structured similar to our sample single-page app where there is one central Javascript file (app.js in the sample) that defines the app's initialization, routing and other stuff, you can use an if.else based on whether the app is loading in an iframe or not. You will need to make some modifications to the html for it to work with your specific app: Ĭonditional initialization in your main app.js file: Please look at the gist for an example of template html you can use. This will not affect user's login experience as Adal saves the start page when user begins the login process and redirects back to the exact location after login is completed. You have to make sure that it matches with the redirect_uri registered in AAD portal. Set redirect_uri property on config to a simple page, that does not require authentication. But, there are workarounds for this that one can use to avoid the entire app reloading again or other errors caused because of this: Since, adal cannot cancel the 302 issued by AAD, it cannot prevent the redirect_uri from getting loaded in the iframe. 
In other cases, if the app's root page requires authentication, it might lead to nested iframes or xframe deny error. Usually, it's the app's root/default page. Since the response is a 302, it results in the html corresponding to the redirect_uri getting loaded in the iframe. AAD returns the token back to the redirect_uri specified in the token request (this redirect_uri must be registered with AAD).
My app is re-loading every time adal renews a token.Īdal uses iframes to renew tokens silently in the background.
0 kommentar(er)
