Hello all!We are on 21.3 Cloud.
We recently enabled the File Upload configuration (From Admin console) - "Block any file with an extension that does not match the underlying type".
Post this change, a set of users started noticing a behavior where when they attach an RTF file, above configuration gets triggered. The RTF file they are trying to upload is generated by an application and the property of the file looks alright. Has anyone experienced such behavior and if so how to get around that?
Thanks so much!
Discussion posts and replies are publicly visible
I'd suggest you open a support case directly with Appian for this. Take one of the RTF files that you can confirm triggers this behavior and attach it to your support ticket for them to analyze.
BTW, did you open one of the affected files in a text / hex editor and verify that its metadata seems to match the ".rtf" file type? Much of the file will look like gibberish when opened as text but usually there's a few snippets of human-readable info at or near the top which MIGHT give a hint as to what the underlying file type is supposed to be.
Based on the documentation -
"If checked, Appian will analyze the file contents of uploaded files to determine the type of the file. If Appian successfully identifies the file type and the type does not match the extension, the file will be blocked regardless of the configured extension list. If the underlying file type or the file type associated with the extension cannot be determined, the extension will be trusted and checked against the extension list above."
Most likely since your RTF file is system generated, it is unable to analyze contents and match it against the file format. In this case Appian will check against the specified extension list. Under "File Extension Blocking" can you double check if "RTF" is allowed is list of extensions or if it is not listed as one of the extensions to be blocked?