The ADAL Android library gives your app the ability to begin using the Microsoft Azure Cloud by supporting Microsoft Azure Active Directory accounts using industry standard OAuth2 and OpenID Connect. This sample demonstrates all the normal lifecycles your application should experience, including:

• Get a token for the Microsoft Graph
• Refresh a token
• Call the Microsoft Graph
• Sign out the user

This app can be used for all Azure AD accounts. It supports both single and multi Organizational scenarios (discussed in steps). It demonstrates how a developer can build apps to connect with enterprise users and access their Azure + O365 data via the Microsoft Graph. During the auth flow, end users will be required to sign in and consent to the permissions of the application, and in some cases may require an admin to consent to the app. The majority of the logic in this sample shows how to auth an end user and make a basic call to the Microsoft Graph.

// Initialize your app with MSAL
AuthenticationContext mAuthContext = new AuthenticationContext(
        MainActivity.this, 
        AUTHORITY, 
        false);


// Perform authentication requests
mAuthContext.acquireToken(
    getActivity(), 
    RESOURCE_ID, 
    CLIENT_ID, 
    REDIRECT_URI,  
    PromptBehavior.Auto, 
    getAuthInteractiveCallback());

// ...

// Get tokens to call APIs like the Microsoft Graph
mAuthResult.getAccessToken()

You will need to have a native client application registered with Microsoft using the Azure portal.

1. Getting to app registration

   • Navigate to the Azure portal.
   • Click on Azure Active Directory > App Registrations.

2. Create the app

   • Click New application registration.
   • Enter an app name in the Name field.
   • In Application type, select Native.
   • In Redirect URI, enter http://localhost.

3. Configure Microsoft Graph

   • Select Settings > Required Permissions.
   • Click Add, inside Select an API select Microsoft Graph.
   • Select the permission Sign in and read user profile > Hit Select to save.
     • This permission maps to the User.Read scope.

4. Congrats! Your app is successfully configured. In the next section, you'll need:

   • Application ID
   • Redirect URI

1. Clone the code.

   git clone https://github.com/Azure-Samples/active-directory-android
   

2. Open the sample in Android Studio.
   • Select Open an existing Android Studio project.

All the configuration for this code sample can be found in the src/main/java/com/azuresamples/azuresampleapp/MainActivity.java.

1. Replace the constant CLIENT_ID with the ApplicationID.

2. Replace the constant REDIRECT URI with the Redirect URI you configured earlier (http://localhost).

1. Select Build > Clean Project.

2. Select Run > Run app.

3. The app should build and show some basic UX. When you click the Call Graph API button, it will prompt for a sign in, and then silently call the Microsoft Graph API with the new token.

1. Checkout the ADAL Android Wiki for more info on the library mechanics and how to configure new scenarios and capabilities.
2. In Native scenarios, the app will use an embedded Webview and will not leave the app. The Redirect URI can be arbitrary.
3. Find any problems or have requests? Feel free to create an issue or post on Stackoverflow with tag azure-active-directory.

We use Stack Overflow with the community to provide support. We highly recommend you ask your questions on Stack Overflow first and browse existing issues to see if someone has asked your question before.

If you find and bug or have a feature request, please raise the issue on GitHub Issues.

To provide a recommendation, visit our User Voice page.

We enthusiastically welcome contributions and feedback. You can clone the repo and start contributing now. Read our Contribution Guide for more information.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

This library controls how users sign-in and access services. We recommend you always take the latest version of our library in your app when possible. We use semantic versioning so you can control the risk associated with updating your app. As an example, always downloading the latest minor version number (e.g. x.y.x) ensures you get the latest security and feature enhanements but our API surface remains the same. You can always see the latest version and release notes under the Releases tab of GitHub.

If you find a security issue with our libraries or services please report it to [email protected] with as much detail as possible. Your submission may be eligible for a bounty through the Microsoft Bounty program. Please do not post security issues to GitHub Issues or any other public site. We will contact you shortly upon receiving the information. We encourage you to get notifications of when security incidents occur by visiting this page and subscribing to Security Advisory Alerts.