![]() ![]() If you are not logged into Google, these options have no effect for you. You can read more about chrome.identity here: Extensions such as Google Keep may require a 1st party login (performed in Google Chrome) and may not work ( see here for more information). To allow WebContainers to run in Brave, you will need to add. Please note that this is considered a 3rd party login. By default, Braves Shields feature blocks Service Workers and cookies from third-party domains. The OAuth token can be used to retrieve personal information like email id, profile. When this option is enabled: It enables chrome.identity for extensions so extensions can retrieve an OAuth token from google to authenticate users. ![]() If you navigate to brave://settings/extensions, you will see an option to enable Allow extensions to use chrome.identity api. Starting 1.51, this option and cookie exception will go away and Brave will prompt per-website when it detects that the website is trying to use third-party cookies for Google Sign-In. When this option is enabled: It adds a third-party cookie exception for so sites using Login with Google can work correctly. If you navigate to brave://settings/socialBlocking, you will see an option to enable Allow Google Login buttons on third party sites. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |