checking whether interaction is in progress inside interceptor

[PramodKumarHK89]

checking whether interaction is in progress. issue #5146

[ghost]

Thank you for your contribution! Please generate change files by running npm run beachball:change from the root of the repo, then answer each prompt and push up the generated files.

[ghost]

Reminder: The next release is scheduled for next week and this PR appears to be stale :(

If changes have been requested please address feedback.
If this PR is still a work in progress please mark as draft.

[jasonnutter]

Apologies for the delay. With this chage, when interaction is in progress, what happens in the interceptor? Nothing?

Also, please add unit tests, and run npm run beachball:change from the root of the repo, complete the prompts, and push the generated change files, thanks!

[jasonnutter]

I think potentially a better approach is to have the interceptor class start listening for inProgress events in the constuctor, and main an internal field (i.e. this.currentInteractionStatus), instead of listening only when acquireTokenInteractively is called.

[tnorling]

Agreed. I also think it would be good to have it call acquireTokenSilent again when inProgress turns back to None. This would prevent a scenario where many calls are queued up all invoking their own interaction back to back to back.

[jasonnutter]

@PramodKumarHK89 We cannot accept this PR in its current form. Please answer the above questions and feedback, or we will close this PR, thanks.

[PramodKumarHK89]

@jasonnutter : Unfortunately, I won't be able to spend time on this due to other priorities. Let me go ahead and close this PR for now and later when I have some bandwidth, I'll accommodate all the suggestions that you guys provided. Thank you so much.