I created a browser extension for my coworkers that enhances the system we use daily but can't modify it.
So far we've been using it locally. Everyone has a copy of the files on their own machine and everytime there's an update I have to notify everyone to manually update it.
I'd like to publish it on the chrome and firefox stores but I would rather not make it public.
Is there a way to publish it privately, so only the people with a link could access and download it ?
I am going to be using youtube API and will need to use a key, but publishing the key would just give it access to all users. How can I hide it? After doing some research I learned that I can create a web server and use that to capture the key? I am new to web server and know little about them? How can I go about creating such server that provides me with a key on request and will the user be able to also call that request if they look around the code?
I have been developing a chrome extension and now I want to create version 2 with database support. For this I am going to use Firebase.
I need to create a file in my extension where I add the details about the firebase connection, api key and url etc..
After reading this question: Where does Chrome store extensions?
I went to look for mine. and boom there it was. I could open the files for the extensions and see the details I added about my firebase connection.
However, I am unsure as to whether I could see it because I am the developer and its on my machine. I do not like the idea of having my access keys available nor url.
Not that I think anyone would sabotage it, but I would hate to be billed for over usage of my requests etc..
I reformatted my drive. Saved all but somehow the p12 is gone.
I tried uploading my .apk to Google Play, an existing app, signed with a new .p12
key and this is the error I get in the image.
Is there a way to make a new .p12 using the numbers they showed me?
Or can I abstract my old .p12 from an app I already uploaded and have copies
of?
Thank you for any advice in this matter.
You can't create a p12 like this, but you can try "migrate" the app to a new certificate, like described here
I never actually tried this, though, so good luck!
I am a developer looking for the best way to set up different schools with their own custom, private extensions (ie School A should be the only one with access to Extension A). Theoretically, I am aware that there are a few ways to get a custom, private extension pushed out on a domain:
Host the .crx on a server and click "Specify a Custom App" in the management console.
Create a Domain App by uploading a zip to the Chrome Web Store
Upload the extension from my developer account to the Chrome Web Store and publish to a single "trusted tester," or make it unlisted
Option (1), hosting the .crx, has not been working. I am not sure why, but the extension is simply not pushing out. I link directly to the crx file, which has the right ID and MIME type, still, no dice. If anyone has any tips or suggestions for getting this to work, I would love to hear them!
Option (2), having the school create a domain app, seems a bit inefficient because it requires all schools to upload their own zip. So essentially I would have to email a zip file to the school, and have them publish it. All updates to the extension will also require a similar process, so this doesn't seem ideal.
I doubt that option (3) would work. If I published to the admin as a "trusted tester", I don't think that the other people in the domain would be able to access it. If it is unlisted, I do not know how an admin could find it in the Chrome Web Store dialog. Also, I would rather avoid security through obscurity.
Has anyone had success with hosting the extension and using the Specify a Custom App feature? Any other suggestions for getting a Custom Extension pushed out by the management console? Thanks so much!
To get option (1) working from the management console, it is important to specify the correct extension id and a valid update xml url (not a crx).
One useful feature Google offers that you can use is getting the extension id and the version from the update request.
For instance, you can create a update.php file that outputs an xml file specific to each extension and version. See http://developer.chrome.com/extensions/autoupdate.html under "Advanced Usage".
For more info on packaging an app or extension for managed chromebooks, see https://support.google.com/chrome/a/answer/2714278?hl=en.