Skip to content
Branch: master
Find file History
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
media
createWorkbenchServicePrincipal.ps1 Fixed the new key generation problem Feb 1, 2019
readme.md

readme.md

Creating a Service Principal to Access Workbench API

Overview

Workbench uses OAuth 2.0 to secure its resources. The Auth provider for Workbench is Azure Active Directory.

In order to use Workbench's API you need to set the Authorization: Bearer <access_token> in your HTTP header. This access token can be obtained in a number of different ways depending on the authentication scenarios.

If you are trying to consume Workbench's API programmatically, you need to use the client credentials flow using a service principal. This document will provide you a script that will create a service principal for you in order to access Workbench programatically.

Access Control

By default any service principal in Workbench's active directory has access to Workbench resources just like any user in that directory. However, just like any user, all service principals by default only have User level access and not Admin level access.

Admin level access is needed if you are trying to create Applications, read all applications, create users, and create role assignments.

Note: Since service principals act like users in a directory they can be assigned to different Workbench "application roles". For example if you are trying to use a service principal to create contracts, you need to assign that service principal to the "creator" role of that application. Today this operation has to be done using the Workbench API as the UI does not allow for service principal role assignment. There is this great article that discusses programatic access of Workbench and application role assignment.

It can be tricky to create a service principal and assign it to Workbench as an Admin, so we've provided an automated a script to create a service principal and you have the option to make that service principal an Admin.

Execution Instructions

To run this script you need to have the AzureAD module installed. Since the AzureAD PowerShell module only works on Windows, we recommend using Azure CloudShell since it comes with with all dependencies installed.

  1. Open Azure CloudShell and select the tenant tied to your Azure Subscription.

CloudShell open

  1. Download the script. You can download the upgrade script automatically by using the command bellow, or you can download it from this repository manually
cd; Invoke-WebRequest -Uri https://aka.ms/createWorkbenchServicePrincipalScript -OutFile createWorkbenchServicePrincipal.ps1

CloudShell download

  1. Locate your Workbench AAD AppId and Tenant and run the following commands. The -MakeAdmin parameter is optional and is only needed if want your service principal to have Admin level access.
./createWorkbenchServicePrincipal.ps1 -TenantName <workbench tenant> -WorkbenchAppId <Workbench AAD AppId> -MakeAdmin (optional)

CloudShell final

  1. You can now use this AppId and Key with any ADAL library to obtain an access token.

Note: The target resource (audience) for accessing Workbench is the Workbench AppId, and the authority is https://login.microsoftonline.com/[tenantName]

Here is an example of a raw http call.:

Method: POST
URL: https://login.microsoftonline.com/<tenant>/oauth2/token
Content-Type: application/x-www-form-urlencoded
Body:
grant_type=client_credentials
&client_id=<service_principal_appId>
&client_secret=<service_principal_key>
&resource=<workbench_appId>
You can’t perform that action at this time.