When we use Repository ‘File Storage’, we have noticed that the file name uploaded to the Windows share repository appears to have been encrypted and differs from what was uploaded by the user.
If we check through the application and look at the database tables, there is no mention of this file name.
Previously using FTP repository in Apps 10, it would store the file with a name like 3001-2279139-1-REV00-1
See below snip shows 1st record uploaded from Cloud (File Storage) vs others from Apps 10 (FTP):
Do we know what is causing this and if this is a security feature that could be turned off?
Best answer by Mathias Dahl
That's an implementation detail in the IFS Cloud File Storage service that you should not care about, because it’s the service that decided how to store its data.
FYI, the file name looks to be Base64 encoded, possibly to overcome problems with characters that are not allowed in a file system. When it comes to Docman, which is probably the biggest use of File Storage, it's not a problem since we already make sure of this, but File Storage is a generic storage service and need to support any file with any name that gets thrown at it.
If you want to see for yourself what the file name "really" is, you can run it through a Base64 decoder, like this:
That's an implementation detail in the IFS Cloud File Storage service that you should not care about, because it’s the service that decided how to store its data.
FYI, the file name looks to be Base64 encoded, possibly to overcome problems with characters that are not allowed in a file system. When it comes to Docman, which is probably the biggest use of File Storage, it's not a problem since we already make sure of this, but File Storage is a generic storage service and need to support any file with any name that gets thrown at it.
If you want to see for yourself what the file name "really" is, you can run it through a Base64 decoder, like this:
@Mathias Dahl This encryption was not happening when we were running on 23R2SU2, after the installation of SU3 it started to encrypt the files and store them in the file share. We are concerned about how this file storage service will access the encrypted and non-encrypted files from the file share.
@Mathias Dahl This encryption was not happening when we were running on 23R2SU2, after the installation of SU3 it started to encrypt the files and store them in the file share. We are concerned about how this file storage service will access the encrypted and non-encrypted files from the file share.
For the sake of correctness, it's not encryption, it's encoding the file names, probably to avoid problems with certain characters.
It sounds strange to introduce this in an SU, but perhaps there were issues with what I just said and we had no choice than to encode the file names.
@Mathias Dahl explanation is correct. This fix was done to get around a few character encoding issues which was found in the FS for Remote and Cloud. The FS internally keeps track of the files with encoded names so any files prior to this change will continue to work without issue.
The file names are base64 encoded, so you can use base64 decode to get the file name, but as said, the actual file name is an implementation detail.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
