After importing the latest solution - toolkit stopped working for test automation

[Arpit-Patel-01]

After upgrading the Toolkit solution to the latest version, the authentication stopped working when testing the agent. I’m using the same configuration as before — Manual Authentication via Entra ID V2 — which worked fine in the previous version.

While investigating the "Test Automation | Run Agent Tests" flow, the error occurred during the user authentication step.

It appears the upgraded version is handling authentication differently, possibly treating the app as a public client but still attempting to send a client_secret.

Please advise if there's a configuration change required for the new version or if this is a bug.

Error Details:

{
"@odata.context": "https://co********.crm4.dynamics.com/api/data/v9.1/$metadata#Microsoft.Dynamics.CRM.cat_AuthenticateEndUserResponse",
"cat_Response": "Error: Token exchange failed. Status: Unauthorized, Response: {
"error": "invalid_client",
"error_description": "AADSTS700025: Client is public so neither 'client_assertion' nor 'client_secret' should be presented.",
"trace_id": "*******-44ba-a2fd-443c450b6b00",
"correlation_id": "***********4bb3-8e0b-a31def0",
"timestamp": "2025-04-10 16:04:47Z"
}"
}

[patilravikiran]

Hi @M365-Developer, please verify your configurations as per latest authentication guide here. There are some changes at Copilot Studio Kit Azure Application. Please use web channel security secret rather token endpoint for direct line connection.

[patilravikiran]

Hi @M365-Developer, Gentle reminder to update on this issue.

[Arpit-Patel-01]

@patilravikiran Thanks for the update, I will definitely check this and will update you on this.

Also I have notice one more bug in file sync functionality.

[patilravikiran]

Thanks @M365-Developer. Please update once you test and share details about file sync issue.

[KavyaPaidisetty]

@patilravikiran I also encountered the same issue after upgrading the solution. After seeing your comments, I enabled web channel security, but I am still getting the same error as mentioned in the above issue.

[patilravikiran]

@KavyaPaidisetty, please refer latest instructions to enable authentication and let me know if you still facing this issue.

[psimolin]

@KavyaPaidisetty if you are still experiencing the issue, please provide redacted screenshot of the related agent configuration

[julienseg1]

I had a similar issue and was finally able to make it work. If I may, documentation regarding the last part (Create agent configuration with end user authentication enabled) could be completed :

• in step 6, we need to enter a Direct Line Secret : a reminder on where to find it on agent config could be usefull + the fields in the form are not mentionned in the instructions : we need first to select "Dataverse"as Secret Location and the paste the Direct Line Secret + I needed to select the Region to be Europe (that was causing the issue for me).
• in step 9, you need to add the Client Secret also

[KavyaPaidisetty]

@patilravikiran @psimolin we have configured with latest Authentication Changes but getting below error

Response:
{
"error": {
"code": "BotError",
"message": "Failed to send activity: bot returned an error"
},
"httpStatusCode": 412
}

[KavyaPaidisetty]

@patilravikiran @psimolin we tried once again configuring authentication ,its working now
thank you so much