Thank you for your prompt reply. Yes, sorry, I have authenticated and used the token into Teams Web API and didn't work, I get the same error as the original post. Please find below some screenshots:
I've set everything under my Azure Portal (client ID, secret, permissions), but I am not sure what else I need to set up in order to send messages through the Teams API.
Thank you!
------------------------------
Kevin Rodriguez
------------------------------
I've set everything under my Azure Portal (client ID, secret, permissions), but I am not sure what else I need to set up in order to send messages through the Teams API. Thank you!
------------------------------
Kevin Rodriguez
------------------------------
@Kevin Rodriguez,
As I mentioned earlier in the thread, the Teams API doesn't expose many actions that can be used with an Application Access token. The majority require that you have a Delegated Access token. Delegated Access tokens require a Client ID, Client Secret, Username, and Password as shown in the example below:
For Username and Password, you could use your own credentials or have a dedicated AD user account created for a digital worker and use that instead.
Cheers,
------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------
As I mentioned earlier in the thread, the Teams API doesn't expose many actions that can be used with an Application Access token. The majority require that you have a Delegated Access token. Delegated Access tokens require a Client ID, Client Secret, Username, and Password as shown in the example below:
For Username and Password, you could use your own credentials or have a dedicated AD user account created for a digital worker and use that instead.
Cheers,
------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------
Thank you for your reply, Eric. That makes sense, I should be using Get Delegated Access Token instead. I tried it with my credentials and I get error "The remote server returned an error: (500) Internal Server Error.". I used the user/password that I log in to Azure Portal, where previous screenshots were taken. I also created another secret, but it didn't matter if the credentials are correct, I get a 500 error. Please see below my configuration:
Is there anything I should be doing beforehand? I can say connection works, as using Get Application Access Token still works and generates a token.
Quick overview:
Thank you so much for all your support!
------------------------------
Kevin Rodriguez
------------------------------
Is there anything I should be doing beforehand? I can say connection works, as using Get Application Access Token still works and generates a token.
Quick overview:
Thank you so much for all your support!
------------------------------
Kevin Rodriguez
------------------------------
@Kevin Rodriguez,
It's been a while since I set up my test environment, but as I recall there's a "trick" to delegated access. The idea behind delegated access is that when an application attempts to work on behalf of another user the user should be presented with the pop-up browser window, notified of the request, and given the option to accept or reject the delegation. In this case, we're not presenting a window for this as this is functionality that's generally run un-attended. Luckily, Microsoft considered this.
When you assign the permissions to the client ID/client secret credential you created in Azure, there's an option to grant admin consent upfront. Just click the button/link referenced below and it will automatically provide the overall consent for the credential. I think that will take care of it for your use of a delegated access token.
Cheers,
------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------
It's been a while since I set up my test environment, but as I recall there's a "trick" to delegated access. The idea behind delegated access is that when an application attempts to work on behalf of another user the user should be presented with the pop-up browser window, notified of the request, and given the option to accept or reject the delegation. In this case, we're not presenting a window for this as this is functionality that's generally run un-attended. Luckily, Microsoft considered this.
When you assign the permissions to the client ID/client secret credential you created in Azure, there's an option to grant admin consent upfront. Just click the button/link referenced below and it will automatically provide the overall consent for the credential. I think that will take care of it for your use of a delegated access token.
Cheers,
------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------
