Windows 10: Endpoint verification google chrome extension API error when changing Gsuite enterprise...

Bndct · Nov 2, 2022

Our company is using google enterprise domain and we're using GCPW to our devices for authentication to laptop/desktop units.We are seeing an API error on google chrome endpoint verification extension whenever there is a password change, and randomly which we don't have any idea why. See image below:This issue will be resolved by locking the device's screen for 15 seconds and relogging back again. Already reported to google and they are pointing us to microsoft since the API is on microsoft end. I just want to be enlighten if this is a normal issue. See answer below by google.Let me know if

:)

Manjunath_H · Nov 2, 2022

Internet Download Manager extension is flagged in Google Chrome.

Hi Frank,

Thank you for writing to Microsoft Community Forums.

We can imagine how difficult it could be and we truly appreciate the time and effort that you have taken to research and work on this issue. However, we would suggest you to follow steps mentioned below and check if it helps.

Right click on Google Chrome icon (shortcut icon) and choose
Properties.

Go to Shortcut tab.

Copy and paste the following parameter in the text box across the
Target field.

-enable-easy-off-store-extension-install

Please refer picture below.

4. Then try adding the extension and check if it resolves the issue.

If the issue still persists, we would suggest you post your query in

Google Chrome support Forums for better assistance.

Regards,

Brink · Nov 2, 2022

New policies for Google Chrome extensions and Google Drive API

Third-party apps and websites create services that millions of people use to get things done and customize their online experience. To make this ecosystem successful, people need to be confident their data is secure, and developers need clear rules of the road. That’s why last year we announced Project Strobe, a root-and-branch review of third-party developer access to your Google account and Android device data.

As a result of our review, we implemented new policies across Gmail and Android to better protect your data. For example, with changes to SMS and Call Log permissions for Android apps, the number of apps with access to this sensitive information has decreased by more than 98 percent. These apps are still able to deliver core services to people just by switching to permissions that access less sensitive data, or by eliminating minor functionality in their apps.

Today, we’re announcing additional changes as a result of Project Strobe, including new policies for Chrome extensions and the Drive API. Here’s what’s new:

Trustworthy Chrome Extensions

There are more than 180,000 extensions in the Chrome Web Store, and nearly half of all Chrome desktop users actively use extensions to customize Chrome and their experience on the web—helping them keep track of to-dos or find shopping deals online. This ability to improve and personalize online experiences depends on a vibrant community of Chrome browser developers.

Last October, we shared our intention to ensure that all Chrome extensions are trustworthy by default. Today, as part of Project Strobe, we’re continuing that effort with additional Chrome Web Store policies. Specifically:

We’re requiring extensions to only request access to the appropriate data needed to implement their features. If there is more than one permission that could be used to implement a feature, developers must use the permission with access to the least amount of data. While this has always been encouraged of developers, now we’re making this a requirement for all extensions.

We’re requiring more extensions to post privacy policies, including extensions that handle personal communications and user-provided content. Our policies have previously required any extension that handles personal and sensitive user data to post a privacy policy and handle that data securely. Now, we’re expanding this category to include extensions that handle user-provided content and personal communications. Of course, extensions must continue to be transparent in how they handle user data, disclosing the collection, use and sharing of that data.

We’re announcing these changes in advance of the official policy rollout this summer to give developers the time needed to ensure their extensions will be in compliance. Developers can learn more about these changes in our FAQ.

Tightening the Drive API

Last fall we updated our user data policy to provide additional guidelines and restrictions for apps seeking to access your Gmail data. Today we’re announcing plans to extend the same policy to Google Drive, which will give you more control over what data third-party apps can access in Drive.

When you connect third-party apps, Drive gives you one central place to keep all your files and helps you easily collaborate with others. With this updated policy, we’ll limit apps that use Google Drive APIs from broadly accessing content or data in Drive. This means we’ll restrict third-party access to specific files and be verifying public apps that require broader access, such as backup services.

These changes will go into effect early next year. Visit the Cloud blog for more details.
Our top priority is to protect user data and keep it safe, while continuing to enable developers to build features that people want and need. As we continue the work of Project Strobe, we’ll also work with our developer partners to give them appropriate time to adjust and update their apps and services.
Click to expand...

Source: https://blog.google/technology/safet...ome-and-drive/

Brink · Nov 2, 2022

New policies for Google Chrome extensions and Google Drive API

Third-party apps and websites create services that millions of people use to get things done and customize their online experience. To make this ecosystem successful, people need to be confident their data is secure, and developers need clear rules of the road. That’s why last year we announced Project Strobe, a root-and-branch review of third-party developer access to your Google account and Android device data.

As a result of our review, we implemented new policies across Gmail and Android to better protect your data. For example, with changes to SMS and Call Log permissions for Android apps, the number of apps with access to this sensitive information has decreased by more than 98 percent. These apps are still able to deliver core services to people just by switching to permissions that access less sensitive data, or by eliminating minor functionality in their apps.

Today, we’re announcing additional changes as a result of Project Strobe, including new policies for Chrome extensions and the Drive API. Here’s what’s new:

Trustworthy Chrome Extensions

There are more than 180,000 extensions in the Chrome Web Store, and nearly half of all Chrome desktop users actively use extensions to customize Chrome and their experience on the web—helping them keep track of to-dos or find shopping deals online. This ability to improve and personalize online experiences depends on a vibrant community of Chrome browser developers.

Last October, we shared our intention to ensure that all Chrome extensions are trustworthy by default. Today, as part of Project Strobe, we’re continuing that effort with additional Chrome Web Store policies. Specifically:

We’re requiring extensions to only request access to the appropriate data needed to implement their features. If there is more than one permission that could be used to implement a feature, developers must use the permission with access to the least amount of data. While this has always been encouraged of developers, now we’re making this a requirement for all extensions.

We’re requiring more extensions to post privacy policies, including extensions that handle personal communications and user-provided content. Our policies have previously required any extension that handles personal and sensitive user data to post a privacy policy and handle that data securely. Now, we’re expanding this category to include extensions that handle user-provided content and personal communications. Of course, extensions must continue to be transparent in how they handle user data, disclosing the collection, use and sharing of that data.

We’re announcing these changes in advance of the official policy rollout this summer to give developers the time needed to ensure their extensions will be in compliance. Developers can learn more about these changes in our FAQ.

Tightening the Drive API

Last fall we updated our user data policy to provide additional guidelines and restrictions for apps seeking to access your Gmail data. Today we’re announcing plans to extend the same policy to Google Drive, which will give you more control over what data third-party apps can access in Drive.

When you connect third-party apps, Drive gives you one central place to keep all your files and helps you easily collaborate with others. With this updated policy, we’ll limit apps that use Google Drive APIs from broadly accessing content or data in Drive. This means we’ll restrict third-party access to specific files and be verifying public apps that require broader access, such as backup services.

These changes will go into effect early next year. Visit the Cloud blog for more details.
Our top priority is to protect user data and keep it safe, while continuing to enable developers to build features that people want and need. As we continue the work of Project Strobe, we’ll also work with our developer partners to give them appropriate time to adjust and update their apps and services.
Click to expand...

Source: https://blog.google/technology/safet...ome-and-drive/

Windows 10: Endpoint verification google chrome extension API error when changing Gsuite enterprise...

Endpoint verification google chrome extension API error when changing Gsuite enterprise...

Endpoint verification google chrome extension API error when changing Gsuite enterprise...

Endpoint verification google chrome extension API error when changing Gsuite enterprise...

Endpoint verification google chrome extension API error when changing Gsuite enterprise... - Similar Threads - Endpoint verification google

Endpoint verification google chrome extension API error when changing Gsuite enterprise...

Google Chrome Extensions

Problem with Chrome extensions (by Google) in Edge

New policies for Google Chrome extensions and Google Drive API

Customizing Google Chrome for Enterprise

Customizing Google Chrome for Enterprise

Using Google Chrome Extensions in firefox?

Install Extensions in Google Chrome

Uninstall Extensions in Google Chrome