In this use case, we're going to describe how you can set up an access token to be used for Interact.
š This use case is optional in case you want toĀ verify user access additionally via tokens in yourĀ Tenant AdministrationĀ > InteractĀ settings.
Steps below refer directly on theĀ Daemon application MSFT help articleĀ and the subchapters.Ā
Create an Azure Application
- Add a new app underĀ app registrationsĀ in the Azure Portal
- Preferably a single tenant application
- No reply-URLĀ needed for the client-credential flow (standard OAuth 2.0 client credentials grant)
š Refer to:Ā https://docs.microsoft.com/en-us/azure/active-directory/develop/scenario-daemon-app-registration
Generate Secret/Certificate
- Generate aĀ secretĀ orĀ certificateĀ which will be used as the applications credentials
š FromĀ https://docs.microsoft.com/en-us/azure/active-directory/develop/scenario-daemon-app-registration
To add credentials to your confidential client application's app registration, follow the steps inĀ Quickstart: Register an application with the Microsoft identity platformĀ for the type of credential you want to add:
Create own Daemon App with .NET/Java/Node/Python
- Based on the language instantiate the confidential client application with the client secret or the certificate
š Refer to the table onĀ https://docs.microsoft.com/en-us/azure/active-directory/develop/scenario-daemon-app-configuration?tabs=dotnet
Acquire a token and pass it to the SDK
- Based on the language instantiate the confidential client application with the client secret or the certificate
š Refer to:Ā https://docs.microsoft.com/en-us/azure/active-directory/develop/scenario-daemon-acquire-token?tabs=dotnet