You might offer your users links to files that are stored in the Spitfire Catalog, but are opened in software that has stripped away authentication. In those instances, users will not be able to open the linked file because Spitfire looks for the authentication before opening the file and does not find any. So, instead, users get a message that says “The page was not displayed because there was a conflict.”
V23+ supports the following solution.
- Edit the link to the file and add &iam=0 to the end. For example:
- Make sure that the file is kept in a folder that all users with the Everyone role can open.
KBA-01841; Last updated: August 28, 2023 at 9:21 am