Assistance Required: WOPI Integration for Editing Word Documents

Question

Dear Microsoft Support Team,

I am currently working on POC to integrating WOPI into my web application to enable users to edit Word documents stored on a server drive using Office Online. Below is an overview of my use case, implementation details, and the issue I am facing.

Use Case:

1. Users can click an "Edit" button on the UI to open a Word document from server drive for editing in an iframe.
2. The documents are stored on a server drive.
3. The focus is on editing Word documents only.
4. When users click the Save button in Word, the edited document should be saved back to the server drive.
5. Before accessing the document for editing, the user should be required to log in to Microsoft.

---

Current Implementation: Technology Stack:

1. Frontend: React.js
2. Backend (WOPI Host): ASP.NET Web API 2
3. WOPI Client: Office Online

WOPI Implementation:

1. Implemented WOPI endpoints: CheckFileInfo, GetFile, PutFile, Lock
2. The CheckFileInfo response includes all required properties for editing, such as BaseFileName, OwnerId, Size, UserId, Version, SupportsLocks=true, SupportsUpdate=true, UserCanWrite=true

Integration Details:

• Created the WOPI Host page where the iframe is dynamically inserted into host html page as per Microsoft’s documentation.
• The WOPI action URL used to open Word in an iframe is: https://word-edit.officeapps.live.com/we/wordeditorframe.aspx?wopisrc=https://abc.com/wopi/files/1&access_token=ACCESS_TOKEN&IsLicensedUser=1
• Here, abc.com is just taken as an example
• Both wopisrc and ACCESS_TOKEN are URL-encoded.
• A JWT access token (ACCESS_TOKEN) is generated in the code.
• File IDs are URL-safe.
• WOPI endpoints (WOPI Host) are publicly accessible over HTTPS.

---

Testing & Debugging:

• WOPI Validator tests were run (attaching results below).
• Currently I am ignoring proof keys as I am working on POC.

• Encountering an issue where the iframe does not display the document.

• The browser console logs the following error:

---

Request for Assistance:

1. Could you please help me understand what might be causing the iframe not to display the document?
2. Is there anything incorrect in my implementation or WOPI configuration?
3. Would CSPP registration be mandatory in my use case, or can we proceed without it?
4. Additionally, are there any costs associated with WOPI integration that we should be aware of?
5. Will any user with a personal or business Microsoft account be able to authenticate via Microsoft to edit a document in our application?

I appreciate your time and assistance. Please let me know if you require any additional details.

Thanks,

Amol