Hacker News new | ask | show | jobs
by 7ewis 2231 days ago
Funnily enough, I was actually trying to figure this out today.

I created a very basic Extension, to modify the new tab page (as it's something you can't set in G Suite the way we'd like it).

I wanted to deploy it our G Suite users, and saw there was an option to deploy via a URL. So I packaged it up in Chrome, put the .crx in an public S3 bucket and set it to force install.

Unfortunately it did nothing... is this not possible? Why is it even an option? Eventually ended up paying for a developer account and submitting it for approval (which was actually super fast).

3 comments

Self-hosting is def an option. Check out "Managing Extensions in Your Enterprise" https://support.google.com/chrome/a/answer/9296680?hl=en. That's probably the single best resource for hosting your own extensions and installing them on managed devices.
You certainly can with G Suite-managed accounts. https://support.google.com/chrome/a/answer/6306504?hl=en

Edit: You seem to say this did nothing for you? Well, good luck troubleshooting.

Yeah, pointed it to the crx, set it to force install and nothing happens.

If I install the crx locally it works fine. No way of seeing any logs to troubleshoot, pinged a message to our reseller but that method is looking like a dead end.

You may be able to reach out to the Chrome Enterprise Browser Support team for assistance. https://support.google.com/chrome/a/answer/4594885?hl=en
You can’t have your users “Load Unpacked...”? That always works for me.
For testing sure, but this needs to go to just over 1000 people.

The only example I can find online on deploying via URL is this:

https://support.securly.com/hc/en-us/articles/360036540753-H...

Can't see many official docs on it at all.

Now I've gone the Developer route I can see you can create internal apps without having to get them approved so think that's my best option now.

This white paper may help https://support.google.com/chrome/a/answer/9296680?hl=en

At some point I want to put together a simple Node.js server and ExtensionSettings policy to demo a basic working setup, but unfortunately that's back-of-the-bus level backseat at the moment.

https://cloud.google.com/docs/chrome-enterprise/policies/?po...

You have to get it signed and deployed as a internal app first.