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...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...