M
markmarko
We have a split database in which the backend resides on a server, and the
front-end is to be deployed on each client machine. In my tests, the user is
greeted with a security error message "A potential security concern has been
identified. Warning: It is not possible to determine that this content came
from a trustworthy source.
You should leave this content disabled unless the content provides critical
functionality and you trust its source."
I used a CurrentUser location when packaging, and still have the message.
My question is, which location needs to be trusted? The location of the
original pre-packaged file? The location that the package will install to?
The location of the backend (which seems silly , since there's no code, even
though I get the same security message if I open the back end directly).
front-end is to be deployed on each client machine. In my tests, the user is
greeted with a security error message "A potential security concern has been
identified. Warning: It is not possible to determine that this content came
from a trustworthy source.
You should leave this content disabled unless the content provides critical
functionality and you trust its source."
I used a CurrentUser location when packaging, and still have the message.
My question is, which location needs to be trusted? The location of the
original pre-packaged file? The location that the package will install to?
The location of the backend (which seems silly , since there's no code, even
though I get the same security message if I open the back end directly).