There are guides available within the ACRM Support portal, which highlight how CRM.launcher can be set-up to work within other browsers than Internet Explorer, such as Firefox and Google Chrome.
Since this is a very common requirement, we'd like to outline the settings made to make CRM.launcher work with Firefox and Chrome within an actual customer environment.
Browse to https://localhost:18188 (where 18188 can be replaced with a custom CRM.launcher port, if the standard port has been overridden). Navigate to the Advanced settings on the page that is shown.
Add the page to the security exceptions
Attempt to edit a document from within CRM.web. The following screen will show up and the document can be edited.
Depending on the client machine's security settings, the following settings may be required, if the above steps don't work and CRM.launcher's certificate is still rejected by the browser
Open a new Tab in Firefox and type in chrome://pippki/content/exceptionDialog.xul
Type https://localhost:18188 into the Location and click Get Certificate
When the certificate info appears, tick Permanently store this exception and then click Confirm Security Exception
Re-test the editing of documents via CRM.web
If there's still an issue, the following settings may be able to resolve it
Add a new property network.security.ports.banned.override by navigating to about:config within Firefox
Assign the CRM.launcher port number to the new property (18188 is the standard port)
Add an Exception for CRM.web (e.g.: http://Server01/crm_web)
2. Google Chrome
Navigate to https://localhost:18188 within Chrome on the client machine and allow the browser to proceed
CRM.launcher should now allow the editing of document from CRM.web
In some cases, the previously mentioned steps might not suffice to permanently enable CRM.launcher in Google Chrome, in which case the following settings can be made
Type chrome://flags/#allow-insecure-localhost into Chrome's address bar and enable the Allow invalid certificates for resources loaded from localhost setting
To test if the settings achieved the desired result of disabling the certificate related warning message that is blocking CRM.launcher, navigate to https://localhost:18188
If it states localhost didn't send any data, then the settings were successful