Skip to main content

Azure Active Directory - How to get access token for Office 365 from a web application or Windows Phone 8

We already saw how Azure Active Directory works does and how we can configure and access it from a WPF or Windows Store application. Unfortunately, not all the stacks that are in this moment on the market have direct support (using a library).
For example, in a WPF application we have NuGet package that can be added to the projects and use directly when we need to get a token from AD. In this moment this is not applicable for a WP8 or a ASP.NET MVC application. I expect that in the future we will have also native support, but until than we need to use direct calls.
The good news is that Active Directory implement OAuth 2 standard. This mean that if you have a library that already use OAuth 2 standard, theoretically you can only update access URL’s and everything should be fine.
The steps that needs to be done to get the access token are not very completed and easy to implement.
First step is to navigate from a browser windows to the resource URL.
[ADLoginAddress]/oauth2/authorize?response_type=code&resource=[Resource]&client_id=[ClientId]&redirect_uri=[RedirectUrl]
The above example is the default one that can be used. For example, to be able to authenticate to AD from Office 365 I used the following address:
https://login.windows.net/[MyPrivateGuid]/oauth2/authorize?api-version=1.0&response_type=code&resource=https://outlook.office365.com/&client_id=[ClientId]&redirect_uri=http://localhost/  
In the moment when we load the above URL, the AD authentication page will be displayed to the client where he needs to insert his credentials. If the authentication will be with success, a code (key) will be returned by our requests through the return URL.
In this moment the returned code (key) can be used to call the specific authority and request an authentication token. In our case the authority URL is https://login.windows.net/common/oauth2/token. The requests needs to be a POST request, where the content needs to contain the code (key), client id, redirect url and client secret key.
Content = “grant_type=authorization_code& code=[CodeFromPreviewsCall]& client_id=[ClientId] &redirect_uri=[RedirectUrl] &client_secret=[ClientSecretKey]"
If the request contains all the needed information, a JSON will be returned that will contain our token. If you are using C#, you can access the token from the result string in this way:
dynamic webToken = JsonConvert.DeserializeObject(response);
string token = webToken.access_token.ToString();
A great sample code related to this was written by Viitorio Bertocci and can be found here: http://www.cloudidentity.com/blog/2014/02/16/a-sample-windows-phone-8-app-getting-tokens-from-windows-azure-ad-and-adfs/

Comments

Popular posts from this blog

Why Database Modernization Matters for AI

  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

[Post Event] Azure AI Connect, March 2025

On March 13th, I had the opportunity to speak at Azure AI Connect about modern AI architectures.  My session focused on the importance of modernizing cloud systems to efficiently handle the increasing payload generated by AI.