Support Azure AD authentication in Explorer #269
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 ADAL JS options to
Config.js, which is commonly overridden when an application-specific Explorer distribution package is created.When
requireADLogin=false, this change has no effect. Otherwise as mentioned in the exampleConfig.js, the configuration options are described in:https://github.com/AzureAD/azure-activedirectory-library-for-js/wiki/Config-authentication-context#configurable-options
Sadly ADAL JS library has a bug that prevents it being managed using Bower: uglifyjs (and minify) fails because it's not compliant with its' strict mode declaration. Excluding ADAL JS from Grunt uglification would require splitting
usemininto subcomponents and doing that reliably is beyond my Grunt-skills.AzureAD/azure-activedirectory-library-for-js#820