<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: OAuth2 access token for report state session in Smart Home Developer Forum</title>
    <link>https://www.googlenestcommunity.com/t5/Smart-Home-Developer-Forum/OAuth2-access-token-for-report-state-session/m-p/740442#M9587</link>
    <description>&lt;P&gt;Thanks for sharing.&lt;/P&gt;
&lt;P&gt;You don't need a separate &lt;STRONG&gt;OAuth2 authorization endpoint&lt;/STRONG&gt; for the Report State API. Instead, your cloud service should already be managing &lt;STRONG&gt;access and refresh tokens&lt;/STRONG&gt; for each user through the initial account linking process. The Report State API simply reuses these existing tokens.&lt;/P&gt;
&lt;P&gt;If an access token expires, your service needs to use the standard &lt;STRONG&gt;OAuth2 refresh token flow&lt;/STRONG&gt; that you've already implemented. Google doesn't have a special endpoint for refreshing tokens for the Report State API—your own OAuth2 server handles the entire token lifecycle.&lt;/P&gt;
&lt;P&gt;The reason for this design is that the Report State API isn't a user-facing process; it's a way for your cloud service to proactively update Google about device state changes. Reusing the existing OAuth2 infrastructure ensures consistent and secure authorization without forcing users to re-authenticate.&lt;/P&gt;</description>
    <pubDate>Tue, 02 Sep 2025 13:53:40 GMT</pubDate>
    <dc:creator>arm_dpe</dc:creator>
    <dc:date>2025-09-02T13:53:40Z</dc:date>
    <item>
      <title>OAuth2 access token for report state session</title>
      <link>https://www.googlenestcommunity.com/t5/Smart-Home-Developer-Forum/OAuth2-access-token-for-report-state-session/m-p/737710#M9474</link>
      <description>&lt;P&gt;According to this article an access token need to be created. I have done this. however, how to refresh this token or is it valid forever ? I wish to get an access token and refresh token using a normal oauth2 client instead of the oauth2L tool&lt;/P&gt;&lt;P&gt;1. Is there a Google report state&amp;nbsp; oauth2 authorization endpoint ? if yes, it this called via implicit ? how to call this ?&lt;/P&gt;&lt;P&gt;2. Is there Google&amp;nbsp; report state oauth2 token endpoint for getting the token for a new session or refresh ?&lt;/P&gt;&lt;P&gt;Why is report state implement via this custom tool instead of a normal oauth2 client&amp;nbsp; ?&lt;/P&gt;&lt;P&gt;&lt;A href="https://developers.home.google.com/cloud-to-cloud/integration/report-state?authuser=0" target="_blank"&gt;https://developers.home.google.com/cloud-to-cloud/integration/report-state?authuser=0&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 23 Aug 2025 13:49:03 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Smart-Home-Developer-Forum/OAuth2-access-token-for-report-state-session/m-p/737710#M9474</guid>
      <dc:creator>debugging</dc:creator>
      <dc:date>2025-08-23T13:49:03Z</dc:date>
    </item>
    <item>
      <title>Re: OAuth2 access token for report state session</title>
      <link>https://www.googlenestcommunity.com/t5/Smart-Home-Developer-Forum/OAuth2-access-token-for-report-state-session/m-p/740442#M9587</link>
      <description>&lt;P&gt;Thanks for sharing.&lt;/P&gt;
&lt;P&gt;You don't need a separate &lt;STRONG&gt;OAuth2 authorization endpoint&lt;/STRONG&gt; for the Report State API. Instead, your cloud service should already be managing &lt;STRONG&gt;access and refresh tokens&lt;/STRONG&gt; for each user through the initial account linking process. The Report State API simply reuses these existing tokens.&lt;/P&gt;
&lt;P&gt;If an access token expires, your service needs to use the standard &lt;STRONG&gt;OAuth2 refresh token flow&lt;/STRONG&gt; that you've already implemented. Google doesn't have a special endpoint for refreshing tokens for the Report State API—your own OAuth2 server handles the entire token lifecycle.&lt;/P&gt;
&lt;P&gt;The reason for this design is that the Report State API isn't a user-facing process; it's a way for your cloud service to proactively update Google about device state changes. Reusing the existing OAuth2 infrastructure ensures consistent and secure authorization without forcing users to re-authenticate.&lt;/P&gt;</description>
      <pubDate>Tue, 02 Sep 2025 13:53:40 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Smart-Home-Developer-Forum/OAuth2-access-token-for-report-state-session/m-p/740442#M9587</guid>
      <dc:creator>arm_dpe</dc:creator>
      <dc:date>2025-09-02T13:53:40Z</dc:date>
    </item>
    <item>
      <title>Re: OAuth2 access token for report state session</title>
      <link>https://www.googlenestcommunity.com/t5/Smart-Home-Developer-Forum/OAuth2-access-token-for-report-state-session/m-p/740735#M9590</link>
      <description>&lt;P&gt;Many thanks. So I need to change my access token&amp;nbsp; for sending report state after google refreshes the token to my OAUTH service?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Sep 2025 04:21:06 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Smart-Home-Developer-Forum/OAuth2-access-token-for-report-state-session/m-p/740735#M9590</guid>
      <dc:creator>debugging</dc:creator>
      <dc:date>2025-09-04T04:21:06Z</dc:date>
    </item>
  </channel>
</rss>

