Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add Azure AD support to the new Explorer.
If
msalConfig
is defined inconfig.js
, force the user through Azure AD redirect-based login into the defined application when opening the Explorer. In the example configuration, credentials are cached inlocalStorage
so they are available in different browser tabs as it's relatively normal to open multiple workflows to different tabs.Because API calls are in a centralized
service.ts
, we cannot easily usemsal-react
hooks to access the authentication. Hence, themsalClient
created in when opening Explorer is somewhat dirtily piggy-backed inconfig
-object toservice.ts
and used to acquire and enrich the API calls withBearer
-token.I haven't tested what happens if all the tokens (including refresh token) are expired. Probably an unclean failure, from which the user can recover by refreshing the browser and starting over. I don't have an environment where API is protected by Azure AD, so I just checked that the
Authorization
token is generated and set correctly.So it's somewhat experimental support, but better than nothing and can be improved based on feedback.