Skip to main content

AzureAD bearer tokens, how to get 'em?

People have asked me about above question in many forums, and I personally have used ADAL (Active Directory Authentication Library) to get one. But here i would show you can use simple Http client to get one.

In following example, I would show you how to get  bearer token for Azure Resource manager;

Before you jump in, you must have created AzureAD application and have it assigned desired permissions to Azure Resource Manager.

In olden days it was done through horrible powershell cmdlets, now days its done through new Azure Portal. (it used to be called ServicePrinciap), ServicePrincipal is actually an instance of your app in AzureAD.

So lets come back to recipe:

a) Fire a Http Client of your choice
b) Set POST method to a your token endpoint for your AzureAD tenant URL https://login.microsoftonline.com/<tenant-id>/oauth2/token
c) Set Content-Type : example : Content-Type: application/x-www-form-urlencoded
d)  Set following parameter as part of your request body:

response_type=client_credentials&client_id=<azureadapp_clientId>&client_secret=<azuread_clientSecret>&resource=https%3A%2F%2Fmanagement.azure.com%2F&grant_type=client_credentials

e) Fire :)

{
  "token_type": "Bearer",
  "expires_in": "3600",
  "ext_expires_in": "0",
  "expires_on": "1481060508",
  "not_before": "1481056608",
  "resource": "https://management.azure.com/",
  "access_token": "_BEARER_TOKEN_"
}


In this request result  you should have now received a bearer token, which you can use further towards Azure Resource Manager.


Remember, key "expires_in" is an epoch time format, so you have to make sure that you have to refresh refresh this token before it expires. which is why ADAL is so good and you do not have to think about such things. :-)

Now you can use another Http call to one of your favorite Azure REST apis and use above "bearer" token as part of authorization header; set value; Authorization bearer <_BEARER_TOKE_>

That's it :)

Remember: The above practice is not good for production env. you have responsibility to store client_id , client_secret in a secure place, practicing above things is not recommended in production env. and ADAL should be part of the game. but for learning purposes, its always good to know how things work in background :)



Comments

Popular posts from this blog

Experience writing a Java based DirXML Driver

Based on the customer project, I wrote a DirXML driver which provision users through Novell Identity Manager 3.5.1 to their company intranet portal ( A Plone System). The portal exposed the RESTful API interfaces. So I started looking first at the Novell SOAP driver to see if it fit our needs. But while reading the driver documentation i felt it required too much XSLT knowledge + more customization and testing on the driver. And again it used the Apache HttpClient, Which is more a HttpClient rather then it targets to any specific protocol implementation. So If you could build SOAP messages at your own so it would help you in transporting these message back and forth between IDM and Application. The Novell SOAP driver comes up with two built in configurations "SPML and DSML", but in my case none of them were suitable. I had always wished to write my own DirXML driver at my own, so I thought why not just take this opportunity to fulfill my wish and at the same time get s...

NetIQ IDM - JDBC statemens using policy builder

Few examples of using JDBC statements using dirxml policies On the Output policy: Handling matching policies with operation-data support: < rule > < description > [DB] Convert Query to DDL doc </ description > < comment name = "author" xml:space = "preserve" > Maqsood Ali Bhatti </ comment > < comment name = "version" xml:space = "preserve" > 5 </ comment > < comment name = "lastchanged" xml:space = "preserve" > Dec 20, 2017 </ comment > < conditions > < and > < if-operation mode = "case" op = "equal" > query </ if-operation > </ and > </ conditions > < actions > < do-append-xml-element expression = ".." name = "jdbc:statement" /> < do-append-xml-element expression = "../jdbc:statement[las...

Novell IdM 3.6 : Creating custom Subscriber PostProcessor Java extension for Delimited Text Driver Part 1

I had chance to write a custom PostProcessor extension for a Delimited Text Driver for Novell Identity Manager,  " t he PostProcessor extension should execute the code under another Windows Domain User account. So I decided to run the driver with Remote Loader Configuration, running the DirXML windows Service under another Windows Domain User Account. " Software and settings in my setup: * Novell Designer 3.0.1 (build  Jan 5, 2009) * Novell Identity Manager 3.6 / Windows Server 2003 R2 * Novell iManager 2.7.2 * Delimited Text Driver 3.6 ver 2.0 (imported configuration  file from Designer 3.0.1) * And the Delimited Text Driver was going to run on the remote server (Remote Loader),  * Java IDE was  (IntelliJIDEA) i started first with digging into documentation of the driver, and i came a cross this section: Using Java Interfaces to Customize File Processing: http://www.novell.com/documentation/idm36drivers/delimited/index.html?page=/documentation/idm36drivers/delimited/data/bkt...