<?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: Gmail Two-Step Authentication in Horizon Desktops and Apps</title>
    <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Gmail-Two-Step-Authentication/m-p/2925723#M97616</link>
    <description>&lt;P&gt;I suggest you create a new config with the settings I provided (use a condition to limit that config to a test user and exlude that test user from the original Chrome config) and test to see if it works there. I have no problems using that config to keep users signed in to Google.&lt;/P&gt;</description>
    <pubDate>Thu, 25 Aug 2022 06:09:46 GMT</pubDate>
    <dc:creator>Mickeybyte</dc:creator>
    <dc:date>2022-08-25T06:09:46Z</dc:date>
    <item>
      <title>Gmail Two-Step Authentication</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Gmail-Two-Step-Authentication/m-p/2925593#M97605</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We have an RDS host set up to provide the Google Chrome app to our users in Horizon.&lt;/P&gt;&lt;P&gt;Most of our users use Chrome to check their personal gmail accounts and have Two-Step (aka Two-Factor) authentication enabled.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Some users are complaining that every time they close the Chrome app and re-open it, they have to authenticate with Two-Factor Authentication again in gmail. It doesn't matter if it is one hour, one day, or whatever, gmail wants them to re-authenticate, and I have confirmed this behavior. This is something they didn't have to do on their personal desktops where Chrome would "remember" them.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is their any way to prevent this 2FA from re-occurring every time they launch Chrome? Maybe a setting in DEM or on the configuration on the RDS host?&lt;/P&gt;&lt;P&gt;We are using Horizon 8 with DEM and we can see that DEM is working because Chrome profiles are loading history, bookmarks, etc when the Chrome app is launched on the RDS host.&lt;/P&gt;&lt;P&gt;Any insight to this would be appreciated.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Aug 2022 14:08:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Gmail-Two-Step-Authentication/m-p/2925593#M97605</guid>
      <dc:creator>GTO455</dc:creator>
      <dc:date>2022-08-24T14:08:56Z</dc:date>
    </item>
    <item>
      <title>Re: Gmail Two-Step Authentication</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Gmail-Two-Step-Authentication/m-p/2925596#M97607</link>
      <description>&lt;P&gt;&lt;a href="https://communities.vmware.com/t5/user/viewprofilepage/user-id/146813"&gt;@GTO455&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;You are probably missing some information of the chrome profile in your DEM configuration.&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is the config I use for Chrome (and also for Edge, but with different folder names):&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[IncludeFiles]
&amp;lt;AppData&amp;gt;\Google\Chrome\User Data\Default\profile.pb

[IncludeRegistryTrees]
HKCU\Software\Google\Chrome
HKCU\Software\Google\EdgeUpdate

[IncludeFolderTrees]
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Profile 1
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Profile 2

[IncludeIndividualFolders]
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data

[ExcludeFolderTrees]
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\[MATCHALL]\Cache
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\[MATCHALL]\Code Cache
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\[MATCHALL]\GPUCache
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\[MATCHALL]\IndexedDB
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\[MATCHALL]\Service Worker\CacheStorage
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\[MATCHALL]\Service Worker\ScriptCache
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\[MATCHALL]\optimization_guide_hint_cache_store
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\[MATCHALL]\optimization_guide_model_metadata_store
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\[MATCHALL]\optimization_guide_prediction_model_downloads&lt;/LI-CODE&gt;&lt;P&gt;This grabs the important parts of the Chrome profile (including extra profiles if they have created them) but excludes the unnecessary cache folders in various locations.&lt;/P&gt;&lt;P&gt;Maybe compare this with your config and adjust where necessary.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Aug 2022 14:38:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Gmail-Two-Step-Authentication/m-p/2925596#M97607</guid>
      <dc:creator>Mickeybyte</dc:creator>
      <dc:date>2022-08-24T14:38:08Z</dc:date>
    </item>
    <item>
      <title>Re: Gmail Two-Step Authentication</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Gmail-Two-Step-Authentication/m-p/2925600#M97609</link>
      <description>&lt;P&gt;I probably should have added my Chrome DEM config in my initial post. It contains most of the same settings as yours (and then some). I found this config &lt;A href="https://www.santoshtech.in/post/capturing-google-chrome-settings-in-non-persistent-vdi-using-dynamic-environment-manager" target="_self"&gt;here&lt;/A&gt;.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[IncludeRegistryTrees]
HKCU\Software\Google\Chrome

[IncludeFiles]
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\First Run
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Local State

[IncludeFolderTrees]
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Profile 1

[ExcludeFolderTrees]
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\Default\Cache
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\Application Cache
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\Cache
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\GPUCache
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\IndexedDB
#&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\Local Storage (this is where Google Earth Settings are saved)
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\Media Cache
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\Session Storage
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\Storage
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\Sync Data
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\Sync Data Backup
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\Web Applications
#These settings were added to reduce Chrome Profile size. Undo them if you run into any issues
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\blob_storage
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\BudgetDatabase
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\data_reduction_proxy_leveldb
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\Feature Engagement Tracker
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\Pepper Data
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\Platform Notifications
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\Service Worker
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\Sync Extension Settings
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\VideoDecodeStats
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\webrtc_event_logs
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\databases
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\Download Service
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\File System
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\GCM Store
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\Thumbnails
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\Code Cache

[ExcludeFiles]
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\Network Action Predictor
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Default\Network Action Predictor-journal
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Profile 1\Network Action Predictor
&amp;lt;LocalAppData&amp;gt;\Google\Chrome\User Data\Profile 1\Network Action Predictor-journal
*.tmp&lt;/LI-CODE&gt;</description>
      <pubDate>Wed, 24 Aug 2022 15:01:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Gmail-Two-Step-Authentication/m-p/2925600#M97609</guid>
      <dc:creator>GTO455</dc:creator>
      <dc:date>2022-08-24T15:01:07Z</dc:date>
    </item>
    <item>
      <title>Re: Gmail Two-Step Authentication</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Gmail-Two-Step-Authentication/m-p/2925723#M97616</link>
      <description>&lt;P&gt;I suggest you create a new config with the settings I provided (use a condition to limit that config to a test user and exlude that test user from the original Chrome config) and test to see if it works there. I have no problems using that config to keep users signed in to Google.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Aug 2022 06:09:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Gmail-Two-Step-Authentication/m-p/2925723#M97616</guid>
      <dc:creator>Mickeybyte</dc:creator>
      <dc:date>2022-08-25T06:09:46Z</dc:date>
    </item>
  </channel>
</rss>

