Intranet URL are no longer opening Windows Explorer after upgrading to v24
Article ID: 386416
Updated On:
Products
Issue/Introduction
In previous versions, user could put a file hyperlink in the documentation so that would open the folder in Windows Explorer.
Example:
file://automic\backup
Resolution
To prevent attacks such as Cross-Site Scripting (XSS) and to prepare for implementing a Content Security Policy, the method of constructing URLs within the AWI has been revised. Simple hyperlinking to URLs and files is now considered insecure and has been replaced with a more secure approach.
Browsers, including Chrome, Edge, and Firefox, block access to local files using the file:// protocol due to significant security risks. For example, attempting to redirect to a local file or with v24, we now offer our customers the ability to integrate their own content through the Automic Automation Help function. This feature is currently available as a beta release that lets you integrate your own customized content in its panel. If you are interested in a demo of this beta feature, please let our team know. This feature will retain your content privately within your system, not sharing your content with Broadcom or anyone else.
https://docs.automic.com/documentation/webhelp/english/AA/24.3/DOCU/24.3/Automic%20Automation%20Guides/Content/_Common/GettingStarted/GS_OnlineHelp.htm#link5
Modifying link creation on the AWI side to allow insecure links is not feasible, as it would trigger security violations. This issue may need to be addressed through a feature request that allows customers to enable insecure links with an understanding of the associated risks.
We recommend reworking current help resources to replace file shares with web URLs or intranet links, which are more compatible with browser security protocols or as a last resort to copy and pasting the url.
Additional Information
The last action would be to reach out directly to the browser vendor to request ways to unblock those restrictions.
Feedback
