Skip to content

Latest commit

 

History

History
68 lines (49 loc) · 5.63 KB

README.md

File metadata and controls

68 lines (49 loc) · 5.63 KB
Raw

Managed Client ADAL Sample

For native applications which can support interative authentication prompts, the Azure Active Directory Authentication Library (ADAL) makes it easy to setup authentication flows for users.

For native applications which cannot support interactive authentication prompts, please check out our Device Profile Sample.

Sample Application

This buildable sample will walk you through the steps to create a client-side console application which uses ADAL to authenticate a user via an interactive prompt and return a list of all projects inside a selected Azure DevOps account.

To run this sample for an Azure Active Directory backed Azure DevOps account you will need:

To run this sample for a Microsoft Account backed Azure DevOps account you will need:

Step 1: Clone or download vsts-auth-samples repository

From a shell or command line:

git clone https://github.com/Microsoft/vsts-auth-samples.git

Step 2: Register the sample application with you Azure Active Directory tenant (AAD backed Azure DevOps account)

If you are a Microsoft Account backed Azure DevOps account please skip this step.
  1. Sign in to the Azure Portal.
  2. On the top bar, click on your account and under the Directory list, choose the Active Directory tenant where you wish to register your application.
  3. On the left hand navigation menu, select Azure Active Directory.
  4. Click on App registrations and select New application registration from the top bar.
  5. Enter a name for you application, ex. "Adal native app sample", choose Native for application type, and enter http://adalsample for the Redirect URI. Finally click create at the bottom of the screen.
  6. Save the Application ID from your new application registration. You will need it later in this sample.
  7. Grant permissions for Azure DevOps. Click Required permissions -> add -> 1 Select an API -> type in and select Azure DevOps (Microsoft Visual Studio Team Services) -> check the box for Delegated Permissions -> click Select -> click Done -> click Grant Permissions -> click Yes.

Step 3: Install and configure ADAL (optional)

Package: Microsoft.Identity.Model.Clients.ActiveDirectory has already been installed and configured in the sample, but if you are adding to your own project you will need to install and configure it yourself.

Step 4a: Run the sample (AAD backed Azure DevOps account)

  1. Navigate to the ADAL C# sample in cloned repo vsts-auth-samples/ManagedClientConsoleAppSample/.
  2. Open the solution file ManagedClientConsoleAppSample.sln in Visual Studio 2017.
  3. Use Nuget package restore to ensure you have all dependencies installed.
  4. Open CS file Program.cs and there is a section with input values to change at the top of the class:
    • azureDevOpsOrganizationUrl - update this with the url to your Azure DevOps/TFS collection, e.g. http://dev.azure.com/organization for Azure DevOps.
    • clientId - update this with the application id you saved from step 2.6 above.
    • replyUri - update this to http://adalsample, you can add other reply urls in azure portal
  5. Build and run the solution. After running you should see an interactive login prompt. Then after authentication and authorization, a list of all projects inside of your account.

Step 4b: Run the sample (Microsoft Account backed Azure DevOps account)

  1. Navigate to the ADAL C# sample in cloned repo vsts-auth-samples/ManagedClientConsoleAppSample/.
  2. Open the solution file ManagedClientConsoleAppSample.sln in Visual Studio 2017.
  3. Use Nuget package restore to ensure you have all dependencies installed.
  4. Open CS file Program.cs and there is a section with input values to change at the top of the class:
    • azureDevOpsOrganizationUrl - update this with the url to your Azure DevOps/TFS collection, e.g. http://dev.azure.com/organization for Azure DevOps.
    • clientId - Do not change this value. It must be used to run the sample successfully.
    • replyUri - Do not change this value. It must be used to run the sample successfully.
  5. Build and run the solution. After running you should see an interactive login prompt. Then after authentication and authorization, a list of all projects inside of your account.