Rsh/azure identity auth

[ramsessanchez]

Added TokenCredentialAuthProvider which uses Azure identity, it takes in a parameter of type TokenCredential to instantiate the class and can be used to authenticate a request by retrieving the access token. Included test classes to test this class, which required a dependency on Mockito to properly test this class.

Example:

//Create a credential of your choice, visit the Azure-Identity SDK for more info
DeviceCodeCredential deviceCodeCred = new DeviceCodeCredentialBuilder()
                .clientId(<CLIENT_ID>)
                .challengeConsumer(challenge -> {System.out.println(challenge.getMessage());})
                .build();
//Using this credential you are able to create an instance of the new TokenCredentialAuthProvider class
TokenCredentialAuthProvider tokenCredAuthProvider = new TokenCredentialAuthProvider(deviceCodeCred,< SCOPES>);
OkHttpClient httpClient = HttpClients.createDefault(tokenCredAuthProvider);
//Create an OKHTTP3 request, service library Requests should be supported on a future date
Request request = new Request.Builder().url("https://graph.microsoft.com/v1.0/me/").build();
//Call the request as you would for MSGraph: 
//https://github.com/microsoftgraph/msgraph-sdk-java#3-make-requests-against-the-service

Copied over some files from the Service library in relation to Authentication, namely the IAuthenticationProvider interface, the AuthConstants class, IHttpRequest interface, the HttpMethod enum class, and the options folder which contains the HeaderOption and Option class. All classes that were copied from the service library were placed into a folder with the same namespace as in the service library to prevent breaking changes.

Added a couple new dependencies to the the build.gradle file:
-Azure-Identity
-Mockito
-Java 8, the current LTS

Let me know if any of the javadocs included need to be clarified or simplified.

[darrelmiller]

@ramsessanchez Can you add some example code to your description that shows how you use a credential object with the SDK client?

[zengin]

Sorry for not realizing this in the first review. GitHub is not great in highlighting a binary in review.

Do we have to add gradle-wrapper.jar into source control? I have read this answer in SO: https://stackoverflow.com/a/20351077, but I am still not convinced. I am hoping this experience has improved since the time the answer was posted to SO.

And if we have to check-in, do we really need two copies of the same binary checked in?

[zengin]

LGTM. Would be nice to have if we can work around not checking in the .jar files.

[hosmanagic-axcient]

How about a test for all of the national and public cloud endpoints (such as in the test above)?

[baywet]

would it add any value though? the code it depends on is already tested for the multiple national clouds.

[hosmanagic-axcient]

In that case, we don't need this test at all, right? Because that other test also covers https://graph.microsoft.com (unless I misunderstood)?

[baywet]

@zengin as far as I can tell it's standard practice to commit the wrapper jar to the repo. The script bootstraps the wrapper which in turns downloads gradle. If you remove it you need to make sure gradle is installed on the local machine, and use the globally installed version instead of the scripts.

[baywet]

@zengin we could update the paths in

msgraph-sdk-java-core/samples/deviceCodeSample/gradlew

Line 83 in f849b69

CLASSPATH=$APP_HOME/gradle/wrapper/gradle-wrapper.jar

We'd just need to be careful next time we update the wrapper not to overwrite it.