Private User-Delegated (OAuth 2.0) Apps
Overview
User-delegated authentication uses OAuth 2.0 to allow users to authorize your app to access their Microsoft data on their behalf. At the end of the OAuth flow, your app receives an access token that enables interaction with Microsoft APIs (Microsoft Graph, Teams, Outlook, etc.).
To use the AutoKitteh server's default Microsoft user-delegated OAuth 2.0 app, see the Default User App guide.
To use daemon (non-interactive) authentication, see the Daemon Apps guide.
Microsoft Documentation
Background information:
- Microsoft identity platform and OAuth 2.0 authorization code flow
- Register an application with the Microsoft identity platform
Create a Microsoft App Registration
Follow the instructions in the Default User App guide to create your Microsoft app registration.
Make a note of the following values for the AutoKitteh connection configuration:
- Application (client) ID
- Client Secret value
- Directory (tenant) ID
AutoKitteh Connections
When you create or edit the connection in an AutoKitteh project:
-
Select the "Microsoft" connection type, if not selected yet
-
Select the "Private user-delegated (OAuth 2.0) app" authentication type
-
Enter the app details from the previous section:
- Client ID (required) - the Application (client) ID
- Client Secret (required) - the client secret value
- Tenant ID (optional) - the Directory (tenant) ID (use
commonfor multi-tenant apps, or leave blank for default)
-
Click the "Start OAuth Flow" button
-
You'll be redirected to Microsoft to authorize the application
-
Review and accept the requested permissions
-
After authorization, you'll be redirected back to AutoKitteh with an active connection