Search the Community
Showing results for tags 'file access protection'.
Found 1 result
I have a solution that is hosted by FMS14 and remotely accessed by my client. My development files have file access protection enabled, and I have authorized the opener file to open the UI file, but they do not have encryption-at-rest (EAR) enabled. Prior to uploading the files to server, I add EAR protection. I am confused because after the encrypted files are uploaded and I go to open them with the opener file (that I thought was authorized), I get the error message that the opener file is not authorized and I am required to input my full access credentials. I am willing to do this, but it means that every time I update the files, I have to re-send my client the opener file that has been authorized for the updated files, and they have to download and replace their opener file for all users and I would like to eliminate this hassle for them. Is there a way to allow the opener file to remain authorized when uploading updated files? Do I need to add authorization for the opener file while the UI and data files have EAR enabled? Thank you for your guidance!