Displaying 1 to 20 from 21 results


  •    Javascript

Active Directory Authentication Library for JavaScript (ADAL JS) helps you to use Azure AD for handling authentication in your single page applications. This library works with both plain JS as well as AngularJS applications. You can learn in detail about ADAL JS installation and usage documented in the ADAL Basics Wiki.

passport-azure-ad - Azure Active Directory Authentication Strategies using Node and Passportjs

  •    Javascript

passport-azure-ad is a collection of Passport Strategies to help you integrate with Azure Active Directory. It includes OpenID Connect, WS-Federation, and SAML-P authentication and authorization. These providers let you integrate your Node app with Microsoft Azure AD so you can use its many features, including web single sign-on (WebSSO), Endpoint Protection with OAuth, and JWT token issuance and validation. passport-azure-ad has been tested to work with both Microsoft Azure Active Directory and with Microsoft Active Directory Federation Services.

node-azure-ad-jwt - An Azure Active Directory Token Validation component for node.js

  •    Javascript

This component makes it super simple to validate a JWT token issued by the Azure Active Directory. Currently the version is not usinge caching this means the certificates will be downloaded from Mirosoft with every verification request. If you are using Azure AAD tokens in every request against your API additional caching would make sense.

MCW-Azure-Blockchain - MCW Azure Blockchain


Northwind Traders is the world's largest food and beverage company. The company has a long history of innovation since its founding more than 150 years ago. Over the last few years, Northwind has been increasing their emphasis on tracking their products from the origin of the raw materials all way through the manufacturing process to the consumer. They pride themselves on being able to certify both the origin and delivery of their products with high accuracy. Jill Anders, the CTO of Northwind Traders has reached out to you to help them build a truly innovative solution to better track their shipments. Jill says, "We need a system that is more secure, more efficient, and will help us lower, not just IT costs, but other costs across the organization." They've heard of Blockchain and Smart Contract technologies, and are thinking these may help them solve this problem.

MCW-OSS-PaaS-and-DevOps - MCW OSS PaaS and DevOps


Best For You Organics Company is one of the leading online health food suppliers in North America, serving customers in Canada, Mexico, and the United States. They launched their highly-successful e-commerce website, which sells subscriptions to their meal service, in 2016, and have been steadily increasing their subscriber-base since. Their service is tailored towards working professionals, who want convenient, reliable access to healthy meal choices, and pre-packaged recipes, without having to speed too much time preparing the meals. Their CIO is a big proponent of Open Source Software, and development of their web application was done using the MERN stack (MongoDB, Express.js, React.JS, Node.js). Their code is hosted in a private GitHub repository. They currently have a continuous integration workflow, triggered by each code check-in/commit in GitHub, using Jenkins.

MCW-Modern-cloud-apps - MCW Modern cloud apps


The Contoso Sports League Association (CSLA) is one of the largest sports franchises and is struggling to keep up with demand from their growing user base. They currently host an e-commerce website and have a backend website that supports their call center, allowing employees to view order information. CSLA would like to modernize their websites and move to the cloud, ultimately moving away from managing infrastructure. They are interested in whether Platform-as-a-Service (PaaS) will meet their needs so they can completely remove the infrastructure management overhead. However, they are concerned about securing their websites and data to meet the stringent PCI (Payment Card Industry) compliance requirements.


  •    TypeScript

The ADAL for node.js library makes it easy for node.js applications to authenticate to AAD in order to access AAD protected web resources. It supports 3 authentication modes shown in the quickstart code below. Current version - 0.1.28 Minimum recommended version - 0.1.22 You can find the changes for each version in the change log.

active-directory-lab-hybrid-adfs - Create a full AD/CA/ADFS/WAP lab environment with Azure AD Connect installed

  •    PowerShell

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

active-directory-python-webapp-graphapi - A Python Web App calling the Microsoft Graph API, leveraging ADAL Python

  •    PowerShell

This sample demonstrates how to build a Python (Flask) web application that authorizes Azure Active Directory users and access data from the Microsoft Graph. To avoid file name length limitations in Windows, clone the repo close to your root directory.

active-directory-android - An android app that uses Azure AD and the ADAL library for authenticating the user and calling a web API using OAuth 2

  •    Java

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. You will need to have a native client application registered with Microsoft using the Azure portal.

active-directory-dotnet-daemon - A Windows console application that calls a web API using its app identity (instead of a user's identity) to get access tokens in an unattended job or process

  •    CSharp

This sample demonstrates a Desktop daemon application calling a ASP.NET Web API that is secured using Azure Active Directory. This scenario is useful for situations where a headless, or unattended job, or process, needs to run as an application identity, instead of as a user's identity. No user interaction is involved.

active-directory-dotnet-daemon-certificate-credential - A

  •    CSharp

The application uses the Active Directory Authentication Library (ADAL) to get a token from Azure AD using the OAuth 2.0 client credential flow, where the client credential is a certificate. In this sample, a Windows console application (TodoListDaemonWithCert) calls a web API (TodoListService) using its app identity. This scenario is useful for situations where headless or unattended job or a windows service needs to run with an application identity, instead of a user's identity.

active-directory-dotnet-deviceprofile - This sample demonstrates how to leverage ADAL

  •    CSharp

The sample uses the OAuth2 device profile flow similar to the one described here. The app is built entirely on .NET Core, hence it can be ran as-is on Windows (including Nano Server), OSX, and Linux machines. To emulate a device not capable of showing UX, the sample is packaged as a console application. The application signs users in with Azure Active Directory (Azure AD), using the Active Directory Authentication Library (ADAL) to obtain a JWT access token through the OAuth 2.0 protocol. The access token is sent to Azure AD's Microsoft Graph API to obtain information about other users in their organization.

active-directory-dotnet-native-headless - A windows desktop program that demonstrates non-interactive authentication to Azure AD using a username & password, and optionaly windows integrated authentication

  •    CSharp

For more information about how the protocols work in this scenario and other scenarios, see Authentication Scenarios for Azure AD. Looking for previous versions of this code sample? Check out the tags on the releases GitHub page.

active-directory-dotnet-webapi-manual-jwt-validation - How to manually process a JWT access token in a web API using the JSON Web Token Handler For the Microsoft

  •    CSharp

This sample demonstrates how to manually process a JWT access token in a web API using the JSON Web Token Handler For the Microsoft .Net Framework 4.5. This sample is equivalent to the NativeClient-DotNet sample, except that, in the TodoListService, instead of using OWIN middleware to process the token, the token is processed manually in application code. The client, which demonstrates how to acquire a token for this protected API, is unchanged from the NativeClient-DotNet sample. When you want to protect a Web API, you request your clients to get a Security token for your API, and you validate it. Usually, for ASP.NET applications this validation is delegated to the OWIN middleware, but you can also validate it yourself, leveraging the System.IdentityModel.Tokens.Jwt library.

active-directory-dotnet-webapi-onbehalfof-ca - A

  •    CSharp

The sample uses the Active Directory Authentication Library (ADAL) in a native client to obtain a token for the user to call the first web service, and also in the first web service to get a token to act on behalf of the user to call the second downstream web API. The downstream web API will have a Conditional Access policy applied that requires Multiple Factors Authentication (MFA). This sample is built on the core active-directory-dotnet-webapi-onbehalfof but adds support for conditional access.


  •    Javascript

Provides JavaScript API to work with Microsoft Azure Active Directory Graph. We provide a full suite of sample applications and documentation on GitHub to help you get started with learning the Azure Identity system. This includes tutorials for native clients such as Windows, Windows Phone, iOS, OSX, Android, and Linux. We also provide full walkthroughs for authentication flows such as OAuth2, OpenID Connect, Graph API, and other awesome features.

AAD.fs - F# WebAPI endpoint protection based on Azure AD roles

  •    F#

The registrated application and principals are kept in your Azure subscription and information about them - in your dotnet user-secrets, when you no longer need them, you can delete them with dotnet fake build -t unregisterSample. Either approach can be used with either version of the requestor.