Some of our clients are adopting Google Chrome and ditching IE/Edge
as the official browser.
All of our application that is dependent on ClickOnce deployment and
SSO login doesn't work in Chrome.
The use of third party extensions is not approved.
We need to build our own extension that the company would maintain.
Can anyone help with the workflow for an extension to enable ClickOnce and SSO in Chrome?
Related
Google is deprecating Chrome apps in favor of Progressive Web Apps (PWA) or Chrome extensions. This leaves extensions as the only way to access Chrome device APIs. I'm looking for a way for my PWA to run along with a Chrome extension in kiosk mode but I'm not sure if it's possible.
The reason I need my PWA to access Chrome device APIs is to get a unique identifier per device to decide which content to display.
As per chromeos.dev: "Previously, Chrome Apps had extra functionality available to them in kiosk mode that is not currently supported by web apps alone. You can continue to use some of this functionality by deploying an extension with your kiosk web application."
Source: https://chromeos.dev/en/education/connecting-an-extension-from-a-kiosk-pwa
It only talks about sending a message from PWA to extension in order to execute a chrome API (like restart) but doesn't talk about how to send information back from extension to PWA. We are also stuck in the same boat- looking for a unique identifier so as to throw content on the chromebox running the PWA. Currently we use chrome.enterprise.deviceAttributes to get serial number and directory device ID in kiosk mode and would need the same once we migrate to PWA. Any luck on this?
I do not really find a google extensions API that launches a desktop application, but I see WebEx did it. https://meetings.webex.com/collabs/#/home Here when you host a meeting, it requires you to install the WebEx Chrome Extension. The extension then launches the desktop application. What is the magic behind it?
Is it the technology they use? https://developer.chrome.com/extensions/nativeMessaging
I see an API called "runtime.connectNative". Does it start a desktop application?
HINT: NPAPI already expired for Chrome. So NPAPI is not what WebEx used
I have a problem getting a chrome extension to work on Windows 10 Technical Preview. I have this extension hosted in Chrome Web store. However when my i run the .exe on my pc, which is supposed to install a client on the pc and an extension on chrome, i cannot see the extension in the chrome extensions.
But when i use the developer version of chrome, i can see the browser prompting me to accept/disable the extension.
What am i missing here? I am pretty new to chrome plugins. Any suggestion/help would be greatly appreciated.
Thanks
Google Chrome (unfortunately) no longer allows private or local crx files to be installed as extensions. You must host it on the Google Chrome app store. From within the store you can make it private to a specific domain, or limit the app to only those within a Google group (they must use their Google account for access to the install).
Deployment of plugins that work within our intranet has suddenly become a major pain. I'm really surprised they couldn't come up with a better solution for this.
https://support.google.com/chrome/a/answer/2663860?hl=en
Currently I am exploring the possibilities and features of Google Chrome apps. As I see to run chrome apps we need to distribute them through chrome App Store. Could we develop a application as a chrome app, which will not need to release to general public or for a limited audience?
Is there anyway that we could package it to native OS executable like .exe in windows or .app in MacOS. So for users who doesn't have chrome installed will also can without any issue. Or at least could we distribute without submitting it to the App Store.
Also I am wondering whether we can run another application through chrome apps? For example I am planing to develop a java application and start with the chrome app.
You can distribute a Chrome App without using the Chrome Web Store, but you'll have to explain to users how to install it, and it's a little tricky: They have to open the Extensions window in Chrome and then drag the installation file to that window. Upon dropping it, there will be a dialog asking them if they want it installed. (They can't just double-click on a file or do anything else that's easy like that.)
Chrome Apps can't directly launch native apps, but they can communicate in various ways with native apps (or any apps) once those other apps are running.
(Some parts of your question are ungrammatical, so I can't be completely sure what you're asking, but the above is what I think you're asking.)
Chrome Extensions are only installable from the Web Store, but Applications can be privately hosted with some provisos: https://developer.chrome.com/extensions/hosting
Google is changing Chrome's policy to no longer allow installation of extensions in any way other than through the Chrome Web Store. However, their wording is a little unclear. They state:
We’ll continue to support local extension installs during development as well as installs via Enterprise policy, and Chrome Apps will also continue to be supported normally.
But it's unclear whether they mean ChromeOS apps, or packaged apps as defined by an "app" section in the manifest.json. Do they mean packaged apps can still be installed outside the Chrome store?
http://blog.chromium.org/2013/11/protecting-windows-users-from-malicious.html
"ChromeOS apps" and "packaged apps as defined by an "app" section in the manifest.json" are one and the same thing. And yes, packaged apps can be installed outside the Chrome Store in their unpackaged form (click the "Development mode" checkbox in chrome://extensions page). Otherwise app development would be seriously hindered.