Authorize Your Kandji Tenant for Okta Workflows

Integrate Kandji's Apple device management solution with Okta Workflows

You can use the Kandji connector to integrate Kandji device management with Okta Workflows, helping to automate critical user lifecycle components that are prone to friction or manual error.

This article covers how to authorize your Kandji tenant for Okta Workflows.

After successfully authorizing your Kandji tenant for Okta Workflows, you can use Kandji connector action cards in Okta Workflows.

Authorize Your Kandji Tenant

When you add a Kandji card to a Workflow for the first time, you'll be prompted to configure the connection. This will enable you to connect your Kandji API token, save your token information, and reuse the connection for future Workflows.

Note: You can create and manage multiple connections from your Connections page.

Create a Kandji Connection

Prerequisites:

• Okta Workflows admin credentials;

• Kandji Connection nickname; 
• Kandji API key; 
• Kandji domain (following the format accuhive.api.kandji.io or accuhive.api.eu.kandji.io).

You can create more than one connection—if, for tenant, you have multiple Kandji tenants or you are testing multiple Kandji API tokens. To make a connection, the Kandji API token must be configured with at least "Device list" permissions. The Kandji API token must allow the appropriate access for the given task. For example, to gather information about all devices, the Kandji API token must have permissions for the following:

To create an API token to use for the Kandji connector:

1. Confirm that your Kandji tenant has API enabled. If it doesn't, contact your Customer Success Manager.
2. Sign in to the Kandji web app with administrator credentials.
3. In the left sidebar, click Settings.
4. Click Access
5. In the API Token section, if your tenant doesn't already have an API Token, click Add API Token
   Otherwise, click Add Token.
6. In the Name field, enter a name such as Okta Workflows.
7. In the Description field, enter a description such as Allow Okta Workflows to use the Kandji API.
8. Click Create.
9. In the Copy your API token dialog, click Copy Token.
10. Store the copied token in a safe place. If you lose the text for the token, you can delete it before you use it and create a new one with the steps above. You'll use this token in step 3 of the next section.
11. Select the checkbox for I have copied the token and understand that I will not be able to see these details again.
12. Click Next.
13. In the Manage API Permissions dialog, click Configure.
14. In the Permissions section, select the checkbox for each area to which you want Okta Workflows to have access. For example, select the checkbox for Blueprints Management to enable all permissions for inspecting and modifying Blueprints. Note: You can click the disclosure triangle to the right of the permission type to display more specific permissions.
15. Review the permissions you've configured for the API token.
16. Click Save then Close. 
17. In the API Token section, confirm that your new token is displayed.
18. In your organization's API URL field, copy or make a note of your Kandji domain.
    

Set Up a Connection

1. In Okta Workflows, from the Connections page or any card, click New Connection.
   
2. In the New Connection window, scroll if necessary, then select Kandji.
   
3. In the Connection Nickname field, enter a unique name that will help you distinguish multiple Kandji tenants or multiple Kandji API keys.
4. In the API key field, enter or paste the text of the API token you generated in step 10 of the previous section.
5. In the Kandji domain field, enter your full Kandji domain (from step 18 of the previous section).

6. Click Create.

   

The Kandji connector is now configured, and this connection is ready to be used with available cards for the connector.

For instance:

1. In Workflows go to the Flows section and click +New Flow.
2. Click Add app action.
3. In the My Connected Apps section, click Kandji.
4. Select a connector card.
   
5. Configure the card and continue building your workflow.