PowerBuilder
PowerBuilder
Microsoft Teams OAuth2 Client Credentials Authentication
See more Microsoft Teams Examples
Demonstrates how to authenticate with OAuth 2.0 using the client credentials grant type.Chilkat PowerBuilder Downloads
integer li_rc
integer li_Success
oleobject loo_Http
oleobject loo_JsonOAuthCC
oleobject loo_Json
oleobject loo_Resp
li_Success = 0
// This requires the Chilkat API to have been previously unlocked.
// See Global Unlock Sample for sample code.
loo_Http = create oleobject
li_rc = loo_Http.ConnectToNewObject("Chilkat.Http")
if li_rc < 0 then
destroy loo_Http
MessageBox("Error","Connecting to COM object failed")
return
end if
// Provide the information needed for Chilkat to automatically fetch the OAuth2.0
// access token as needed.
// This is the new "Integrated OAuth2 Client Credentials" feature introduced in Chilkat v9.5.0.96.
loo_JsonOAuthCC = create oleobject
li_rc = loo_JsonOAuthCC.ConnectToNewObject("Chilkat.JsonObject")
// --------------------------------------------------------------------------------------------------------
// You'll need to have registered an app in Azure beforehand.
//
// Note: Creating a Team requires the following Application permissions:
// Team.Create, Teamwork.Migrate.All, Group.ReadWrite.All**, Directory.ReadWrite.All**
//
// See How to Create an Azure App Registration for OAuth 2.0 Client Credentials
// --------------------------------------------------------------------------------------------------------
// Use the values from your App Registration in Azure.
loo_JsonOAuthCC.UpdateString("client_id","e1cd2318-xxxx-4916-bfd6-xxxxxxxxxxxx")
loo_JsonOAuthCC.UpdateString("client_secret","K.d8Q~~RoJxxxxvCj_u_xxxxxxxxxxxxxxxxxxxxx")
// You'll always use this scope for client credentials, because the allowed actions
// are determined by the App Permissions defined when you registered the app in Azure.
loo_JsonOAuthCC.UpdateString("scope","https://graph.microsoft.com/.default")
// The token endpoint includes your tenant ID. Use your tenant ID (not the tenant ID shown here).
loo_JsonOAuthCC.UpdateString("token_endpoint","https://login.microsoftonline.com/112d7ed6-71bf-4eba-a866-738364321bfc/oauth2/v2.0/token")
// Provide the OAuth2 information. Chilkat will use this information to automatically fetch the OAuth2 access token as needed,
loo_Http.AuthToken = loo_JsonOAuthCC.Emit()
// ------------------------------------------------------------------------------
// To create a Microsoft Team, we want to send an HTTP request like the following:
//
// Note: The following is the minimal JSON for a request using Applicaton permissions (i.e. the access token retrieved using the client credentials grant).
//
// POST https://graph.microsoft.com/v1.0/teams
// Content-Type: application/json
//
// {
// "template@odata.bind":"https://graph.microsoft.com/v1.0/teamsTemplates('standard')",
// "displayName":"My Sample Team",
// "description":"My Sample Team�s Description",
// "members":[
// {
// "@odata.type":"#microsoft.graph.aadUserConversationMember",
// "roles":[
// "owner"
// ],
// "user@odata.bind":"https://graph.microsoft.com/v1.0/users('0040b377-61d8-43db-94f5-81374122dc7e')"
// }
// ]
// }
loo_Json = create oleobject
li_rc = loo_Json.ConnectToNewObject("Chilkat.JsonObject")
loo_Json.UpdateString("~"template@odata.bind~"","https://graph.microsoft.com/v1.0/teamsTemplates('standard')")
loo_Json.UpdateString("displayName","My Sample Team")
loo_Json.UpdateString("description","My Sample Team�s Description")
loo_Json.UpdateString("members[0].~"@odata.type~"","#microsoft.graph.aadUserConversationMember")
loo_Json.UpdateString("members[0].roles[0]","owner")
loo_Json.UpdateString("members[0].~"user@odata.bind~"","https://graph.microsoft.com/v1.0/users('4ee732c3-322e-4a6b-b729-2fd1eb5c6004')")
loo_Json.EmitCompact = 0
Write-Debug loo_Json.Emit()
loo_Http.SetRequestHeader("Content-type","application/json")
loo_Resp = create oleobject
li_rc = loo_Resp.ConnectToNewObject("Chilkat.HttpResponse")
li_Success = loo_Http.HttpJson("POST","https://graph.microsoft.com/v1.0/teams",loo_Json,"application/json",loo_Resp)
if li_Success = 0 then
Write-Debug loo_Http.LastErrorText
destroy loo_Http
destroy loo_JsonOAuthCC
destroy loo_Json
destroy loo_Resp
return
end if
// A successful response is indicated by a 202 response status code and an empty response body.
Write-Debug "Response Status Code: " + string(loo_Resp.StatusCode)
Write-Debug "Response Body:"
Write-Debug loo_Resp.BodyStr
if loo_Resp.StatusCode >= 400 then
Write-Debug "Response Header:"
Write-Debug loo_Resp.Header
Write-Debug "Failed."
end if
destroy loo_Http
destroy loo_JsonOAuthCC
destroy loo_Json
destroy loo_Resp