/
Microsoft Teams Bot Service: Could not authenticate Alert

Microsoft Teams Bot Service: Could not authenticate Alert

Could not authenticate Alert

Content

Alert: Could not authenticate
Service: <SERVICE_NAME>
Computer name: <COMPUTER_NAME>
Alert id: .122.0.7
Time: <TIME> (UTC)
Severity: Critical

Description:
Could not authenticate

Alert attributes:
Description (OID: .200.1): Could not request OAuth token for tenant: <TENANT_ID>. Check the credentials.
<ERROR_MESSAGE>
Tenant id (OID: .200.16): <TENANT-ID>

– OR –

Description (OID: .200.1): Could not validate JWT Token of inbound request for tenant: <TENANT_ID>

JWT Token: <JWT_TOKEN>

<ERROR_MESSAGE>
Tenant id (OID: .200.16): <TENANT_ID>

 

Cause

This alert is sent if the Bot service is not able to retrieve an OAuth token for the outbound HTTP requests or the bot service is not able to validate the inbound HTTP requests.

Resolution

 

If you receive such an alert, please contact the support service and send the teamsbot.log from the Verba Bot Server.

Log files are available under "APPLICATION_FOLDER\log" (by default C:\Program Files\Verba\log) folder on each server.

Related content

Microsoft Teams Bot Service: Could not join call Alert
Microsoft Teams Bot Service: Could not join call Alert
More like this
Microsoft Teams Bot Service: Unexpected call termination Alert
Microsoft Teams Bot Service: Unexpected call termination Alert
More like this
Microsoft Teams Bot Service: Call timed out Alert
Microsoft Teams Bot Service: Call timed out Alert
More like this
Microsoft Teams Bot Service: No available recorder Alert
Microsoft Teams Bot Service: No available recorder Alert
More like this
Microsoft Teams Bot Service: Recorder Connection Up Alert
Microsoft Teams Bot Service: Recorder Connection Up Alert
More like this
Microsoft Teams Bot Service: Recorder Connection Down Alert
Microsoft Teams Bot Service: Recorder Connection Down Alert
More like this