Add state parameter in authentication requests

[hswimmer]

We use state parameter for single redirect url for many sites.

with msal we send:

await msal.loginPopup({
        scopes: scopes,
        state: requestState
      })

any idea how we can send it with InteractiveBrowserCredential

[sadasant]

Hello @hswimmer ! I'll be doing my best to help.

We should definitely support this.

We'll start working on this issue in a couple of weeks. I'll make sure to give you an update of when we'll release this feature!

[sadasant]

I'll leave this link for context, for myself: https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/3a730d5ad842eaa8fc643015817cd7c20415e921/lib/msal-browser/src/request/PopupRequest.ts#L20

[sadasant]

@hswimmer would it make sense for you if the InteractiveBrowserCredential accepted a new constructor option called loginState? to then pass that option to MSAL’s popup/redirect login requests?

[sadasant]

@hswimmer do you have a concrete example of how this property would help you?

[hswimmer]

We have several clients app authenticated with AAD and using @azure/storage-blob package
We use one redirect url for all of them and from the redirect url we navigate back to the original site by url we send in state parameter.
When trying to use InteractiveBrowserCredential we send the 'global' redirect url but no way to send the original site url

[sadasant]

@hswimmer thank you. We’ll have an update in about a week.

[sadasant]

@hswimmer it’s been a week and we do have an update. We’ll be discussing about this suggestion with the team in the following days. We want to make sure we’re all aligned on what’s the best way forward. I’ll keep you posted!

[sadasant]

@hswimmer, after thorough conversations with my team, we’ve decided to postpone adding support for this.

The best we can do in the short term is provide documentation on creating a custom credential that would use @azure/msal-browser underneath. For that purpose, I’ve made this issue: #15573

We want to have a better browser story in the long term, though. We’ll make sure to keep you posted.

[hswimmer]

@sadasant thanks for the update. waiting for documentation.

[sadasant]

@hswimmer If you find some time to review what we’re adding in this PR, your feedback is appreciated: #15573

I’ll close this issue for now. Thank you for submitting your feedback so far! This issue has helped us a lot. We’ll be working on a better browser-oriented experience through the upcoming months and well into next year.