About the function of IFS EE Link Handler

I am aware of the following information from previous responses.
Please confirm that this perception is correct.

The only two cases where ifs.Fnd.Explorer.application needs to be replaced are when the encryption certificate expires and when ifs.Fnd.Explorer.application is updated.

When IFS Applications 10 users use the IFS Enterprise Explorer link in Chrome, if the extension is not available, the “ifs.Fnd.Explorer.application” will be downloaded, but there is no need to replace it. This is a specification when using chrome and does not affect other functions.

Hi ​@lakglk 

Is this a subject you could advise on please?

Thank you in advance,
Grzegorz

Hi,

If I’m understanding the situation correctly, an end user is attempting to launch IFS Applications on Chrome by clicking a ClickOnce web deployment link (eg. a link that ends with /Ifs.Fnd.Explorer.application). Instead of launching the application to the login screen, it downloads the deployment manifest (Ifs.Fnd.Explorer.application) as a file.

This is generally the case when you’re using Google Chrome without properly setting up the IFS Enterprise Explorer Link Handler extension.

Do note that recently Google Chrome disabled all Manifest V2 extensions. This includes our “old” extension “IFS EE Link Handler”. We recommend end users or admins to remove this extension and use our Manifest V3 complaint extension.

The process is outlined in this KB article: https://support.ifs.com/csm?id=kb_article&sys_id=9483cdaac3942ad4dfc7003599013176

In any case, this doesn’t work, let me know. You can also use Microsoft Edge as an alternative, which supports ClickOnce deployments out of the box (without any extensions).