cancel
Showing results for 
Search instead for 
Did you mean: 

Failed to add authorization token to the HTTP header

matekatona
Community Member

Hello!

I integrated my devices to Google Gome with cloud2cloud.

I use Auth0 idp toimplement oaut2. IT works about 24 hours, until my access token expires. IT seems to google not refreshing auth token. I don't see any log on auth0 side.

 

 

I get "Failed to add authorization token to the HTTP header" and EXECUTION_GAL_NOT_FOUND.

And i also get another error with "Agent responded empty JSON"

Anybody any idea? What is the problem?

1 Recommended Answer

Suc1
Solutions Expert
Solutions Expert

The "EXECUTION_GAL_NOT_FOUND" error occurs because your access token expired and isn't refreshing properly. When this happens, Google Home devices can't authenticate to your service.

Google needs to automatically refresh tokens once access tokens expire, which typically happens after 24 hours as you've noticed.

For a proper implementation example, I recommend checking our Smart Home Node.js samples repository: https://github.com/actions-on-google/smart-home-nodejs

This repository contains complete examples of:

  • OAuth 2.0 flow setup with proper refresh token handling
  • Token storage and management
  • Expired token detection logic
  • Automatic token refresh implementation
  • Authorization header handling for all requests

Additionally, our official documentation provides detailed guidance: https://developers.google.com/assistant/smarthome/develop

After implementing these patterns from our sample code, your authorization token issues should be resolved. The key is ensuring your Auth0 implementation correctly handles the refresh token workflow when the access token expires.

 

View Recommended Answer in original post

2 REPLIES 2

Suc1
Solutions Expert
Solutions Expert

The "EXECUTION_GAL_NOT_FOUND" error occurs because your access token expired and isn't refreshing properly. When this happens, Google Home devices can't authenticate to your service.

Google needs to automatically refresh tokens once access tokens expire, which typically happens after 24 hours as you've noticed.

For a proper implementation example, I recommend checking our Smart Home Node.js samples repository: https://github.com/actions-on-google/smart-home-nodejs

This repository contains complete examples of:

  • OAuth 2.0 flow setup with proper refresh token handling
  • Token storage and management
  • Expired token detection logic
  • Automatic token refresh implementation
  • Authorization header handling for all requests

Additionally, our official documentation provides detailed guidance: https://developers.google.com/assistant/smarthome/develop

After implementing these patterns from our sample code, your authorization token issues should be resolved. The key is ensuring your Auth0 implementation correctly handles the refresh token workflow when the access token expires.

 

matekatona
Community Member

I did not implemented my own oauth2. I use third party idp called auth0.

 

I do not see any logs on auth0 side about the token request. I think Google does not call the token endpoint.