Forum Discussion
NimbostratusUsing the iapp for sharepoint: Documents can not be edited
Hi there,
We provide access to sharepoint 2010 via the bigip, version 11.3 (soon will be updated). For configuration we used the iapp.
Everything seems to work fine, but editing office documents in the locally installed office won't work. When I try to edit e.g. a pptx the following message appears, indicating that the internet address is invalid.
It seems that powerpoint cannot access the document. Is there a fix for this?
Regards, Alexander
6 Replies
- Kevin_Stewart
Employee
Are you using APM? If so, can you verify whether or not session cookie persistence is set in the access policy?
Alexander_01_13Thank you for resolving this question.
You made my day!
Will this work with Sharepoint 2013 as well?
Regards,
Alexander
- Kevin_Stewart
Yes it should. It's an unfortunate conflict between APM's default cookie-based session management and the lack of integration between SharePoint and its spawned applications (Office products, SP explorer, etc.) that cannot use the browser's in-memory session cookies. Setting the persistent option in the policy creates a file-based cookie that the spawned applications can consume.
FYI, the v11.4 version of the template sets the persistent cookie option by default. In v11.3, you would need to disable strictness on the iApp and set it manually (if you are using the on-box template; the version of DevCentral for v11.3 and earlier will set it automatically as well).
Carlos_13563Cirrus
We had the same problem with users trying to edit a document inside Sharepoint and when they click edit for a MS Word document, Word would open, but would not open the doc. After we enable Persistent Cookie we can open the document, but it's asking to authenticate again, that we do and we can open the document with no problems. Is there a way to not prompt authentication again?- Have you added the SharePoint site to the trusted sites list in IE, and set the User Authentication>Logon setting for that zone to "Automatic logon with current user name and password"? If that doesn't help, there is a known bug with the Office clients not honoring persistent cookies. You would need to take a tcpdump or other traffic capture to confirm that the clients aren't sending the cookies. F5 is monitoring that bug and will update the documentation ASAP.
