Access to d!nk through proxy and Anti-virus

Follow

If you're having problems using the d!nk admin (For example: can't upload content or some of the covers are not showed correctly) or the app (for example: some publications don't open) your IT administrator will need to whitelist the urls that are being used by d!nk in the proxy or Antivirus.

Whitelisting of URL in Proxy

We use the following domains:

  • dink-kiosk.appspot.com 
  • grow.dink.eu
  • https://s3-eu-west-1.amazonaws.com/eu.dink.cdn.pdf/*
    https://s3-eu-west-1.amazonaws.com/eu.dink.cdn.videos/*
    https://s3-eu-west-1.amazonaws.com/eu.dink.cdn.zipbasededitions/*
    https://s3-eu-west-1.amazonaws.com/eu.dink.cdn.zips/*

for Dynamic Value, values are fetched by calling an API at https://dink-kiosk.appspot.com
We're using a GET request but this is preceded by an OPTIONS request.
The OPTIONS method must be allowed by the configuration.

the d!nk app does not use client certificates and certificate pinning.

Specifically for the Windows app, we have incorporated NTLMv2 into the d!nk app to allow authentication through the corporate proxy settings.

Whitelisting in Anti-Virus

System admin must set "dink.exe" as an exception in the anti-virus. Because dink does contain some encryption code, the Anti-virus could be marking dink as false positive (thinks dink is "ransomware"). Example: https://esupport.trendmicro.com/en-us/home/pages/technical-support/1059964.aspx

If whitelisting needs to happen based on filepath, then it is advised to whitelist both the LocalContentFolder and ApplicationFolder, example:
- C:\Users\username\AppData\Local\Packages\dINKbvba.dNK_83grspkmw1tr2
- C:\Program Files\WindowsApps\dINKbvba.dNK_1.2.0.166_x64__83grspkmw1tr2
In order to avoid updating the whitelist after each app update, it is advised to whitelist using wildcard \dINKbvba.*

Have more questions? Submit a request

Comments

Powered by Zendesk