I have a situation where i'm not able to test the FPS for one of the core use cases. details are below

I have 2 top level sites www.site11.com and www.site22.com and both of them embeds www.connect11.com website, and now when i first visit www.site11.com , i could go ahead and login to www.connect11.com and everything works, and then i try visiting to set22.com which doesn't seem have access to the login credentials which were set earlier.

My understanding so far

• Connect11.com within site11.com would set a cookie on site11.com cookie partition and hence the same isn't available when i visit site22.com which make sense
• so to allow this access i used FPS by locally launching chrome by using below command
  open -a "Google chrome" --args --enable-features="FirstPartySets:FirstPartySetsClearSiteDataOnChangedSets/1,StorageAccessAPI,StorageAccessAPIForOriginExtension,PageInfoCookiesSubpage,PrivacySandboxFirstPartySetsUI" \ --use-first-party-set="{\"primary\": \"https://www.site11.com\", \"associatedSites\": [\"https://www.site22.com\"]}" \ https://www.site22.com:2000

but couldn't get the seamless login to work between the 2 top level sites for the embedded widget.

Are there any pointer here on how to fix this setup, i did use storage access APIs to grant access but didn't work.

Note: i could get this working if i associate connect11.com as a associatedSites which i would like to avoid as it's a SasS solution which provides embedded chat widget functionality