Node.js

Outlook Contact OAuth2 Access Token - Using Azure AD v2.0 Endpoint

See more Outlook Contact Examples

Demonstrates how to get a Microsoft Graph OAuth2 access token from a desktop application or script using scopes for Outlook Contact.

Microsoft Graph supports two authentication providers:

• To authenticate users with personal Microsoft accounts, such as live.com or outlook.com accounts, use the Azure Active Directory (Azure AD) v2.0 endpoint.
• To authenticate users with enterprise (that is, work or school) accounts, use Azure AD.

This example uses the Azure Active Directory (Azure AD) v2.0 endpoint.

Node.js

NODEJS_PRELUDE

function chilkatExample() {

    var success = false;

    //  This example requires the Chilkat API to have been previously unlocked.
    //  See Global Unlock Sample for sample code.

    //  See more Microsoft Graph OAuth2 examples:
    //  
    //  Microsoft Graph OAuth2 App Authentication using Azure AD
    //  Microsoft Graph OAuth2 Client Credentials Grant Flow
    //  Microsoft Graph -- Renew Expiring Access Token (Azure AD v2.0 Endpoint)
    //  Microsoft Graph -- Renew Expiring Access Token (Azure AD Endpoint)
    //  Decode Microsoft Graph ID Token
    //  Microsoft Graph Revoke OAuth2 Access Tokens

    var oauth2 = new chilkat.OAuth2();

    //  This should be the port in the localhost callback URL for your app.  
    //  The callback URL would look like "http://localhost:3017/" if the port number is 3017.
    oauth2.ListenPort = 3017;

    oauth2.AuthorizationEndpoint = "https://login.microsoftonline.com/common/oauth2/v2.0/authorize";
    oauth2.TokenEndpoint = "https://login.microsoftonline.com/common/oauth2/v2.0/token";

    //  Replace these with actual values.
    oauth2.ClientId = "MICROSOFT-GRAPH-CLIENT-ID";
    //  This is your app password:
    oauth2.ClientSecret = "MICROSOFT-GRAPH-CLIENT-SECRET";

    oauth2.CodeChallenge = false;
    //  Provide a SPACE separated list of scopes.
    //  See https://developer.microsoft.com/en-us/graph/docs/authorization/permission_scopes 

    //  Important: To get a refresh token in the final response, you have to ask for "offline_access" scope
    oauth2.Scope = "openid profile offline_access user.readwrite contacts.readwrite files.readwrite";

    //  Begin the OAuth2 three-legged flow.  This returns a URL that should be loaded in a browser.
    var url = oauth2.StartAuth();
    if (oauth2.LastMethodSuccess == false) {
        console.log(oauth2.LastErrorText);
        return;
    }

    //  Launch the system's default browser navigated to the URL.
    success = oauth2.LaunchBrowser(url);
    if (success == false) {
        console.log(oauth2.LastErrorText);
        return;
    }

    //  Now wait for the authorization.
    //  We'll wait for a max of 30 seconds.
    var numMsWaited = 0;
    while ((numMsWaited < 30000) && (oauth2.AuthFlowState < 3)) {
        oauth2.SleepMs(100);
        numMsWaited = numMsWaited+100;
    }

    //  If there was no response from the browser within 30 seconds, then 
    //  the AuthFlowState will be equal to 1 or 2.
    //  1: Waiting for Redirect. The OAuth2 background thread is waiting to receive the redirect HTTP request from the browser.
    //  2: Waiting for Final Response. The OAuth2 background thread is waiting for the final access token response.
    //  In that case, cancel the background task started in the call to StartAuth.
    if (oauth2.AuthFlowState < 3) {
        oauth2.Cancel();
        console.log("No response from the browser!");
        return;
    }

    //  Check the AuthFlowState to see if authorization was granted, denied, or if some error occurred
    //  The possible AuthFlowState values are:
    //  3: Completed with Success. The OAuth2 flow has completed, the background thread exited, and the successful JSON response is available in AccessTokenResponse property.
    //  4: Completed with Access Denied. The OAuth2 flow has completed, the background thread exited, and the error JSON is available in AccessTokenResponse property.
    //  5: Failed Prior to Completion. The OAuth2 flow failed to complete, the background thread exited, and the error information is available in the FailureInfo property.
    if (oauth2.AuthFlowState == 5) {
        console.log("OAuth2 failed to complete.");
        console.log(oauth2.FailureInfo);
        return;
    }

    if (oauth2.AuthFlowState == 4) {
        console.log("OAuth2 authorization was denied.");
        console.log(oauth2.AccessTokenResponse);
        return;
    }

    if (oauth2.AuthFlowState !== 3) {
        console.log("Unexpected AuthFlowState:" + oauth2.AuthFlowState);
        return;
    }

    console.log("OAuth2 authorization granted!");
    console.log("Access Token = " + oauth2.AccessToken);

    //  Get the full JSON response:
    var json = new chilkat.JsonObject();
    json.Load(oauth2.AccessTokenResponse);
    json.EmitCompact = false;

    //  The JSON response looks like this:

    //  {
    //    "token_type": "Bearer",
    //    "scope": "openid profile User.ReadWrite Contacts.ReadWrite Files.ReadWrite ...",
    //    "expires_in": 3600,
    //    "ext_expires_in": 3600,
    //    "access_token": "EwBAA8l6B...",
    //    "refresh_token": "MCRMdbe...",
    //    "id_token": "eyJ0eXA..."
    //  }

    console.log(json.Emit());

    //  Save the JSON to a file for future requests.
    var fac = new chilkat.FileAccess();
    fac.WriteEntireTextFile("qa_data/tokens/outlookContacts.json",json.Emit(),"utf-8",false);

}

chilkatExample();