Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Word Addin content is blocked because it isn't signed by a valid certificate when being IIS hosted in a website having a (*) wildcard certificate. #2613

Closed
cebrotea opened this issue Jun 6, 2022 · 2 comments
Assignees
Labels
Area: Word Issue related to Word add-ins Needs: triage 🔍 New issue, needs PM on rotation to triage ASAP Type: product bug Bug in the Office Add-ins platform or Office JavaScript APIs

Comments

@cebrotea
Copy link

cebrotea commented Jun 6, 2022

Word addin not loading when is hosted in a website that has a wildcard certificate *( Issued to: .domain.com)
Changing the website certificate to a named certificate (Issued to: machineName.domain.com) fixes the problem.

Your Environment

  • Platform [PC desktop, Mac, iOS, Office on the web]: PC
  • Host [Excel, Word, PowerPoint, etc.]: WORD
  • Office version number: 2108 (Microsoft Word for Microsoft 365 MSO (16.0.14326.20850) 64 bit)
  • Operating System: Windows 10 Pro 10.0.19044 Build 19044
  • Browser (if using Office on the web): ______

Expected behavior

The addin should load no matter if the certificate is issued as a wildcard certificate

Current behavior

The addin cannot be loaded and it shows the following message: The content is blocked because it isn't signed by a valid certificate

Steps to reproduce

  1. Create an IIS website that has a wildcard certificate ( *( Issued to: .domain.com) )
  2. Deploy the addin files in the website location
  3. Open word and try to open a taskpane that points to the addin

Context

Hosting the office js addin in a SAAS Environment is not possible because of this issue

Useful logs

image

Thank you for taking the time to report an issue. Our triage team will respond to you in less than 72 hours. Normally, response time is <10 hours Monday through Friday. We do not triage on weekends.

@ghost ghost added the Needs: triage 🔍 New issue, needs PM on rotation to triage ASAP label Jun 6, 2022
@peronald peronald added Area: Word Issue related to Word add-ins Type: product bug Bug in the Office Add-ins platform or Office JavaScript APIs labels Jun 6, 2022
@samantharamon
Copy link

Thank you for reporting this, @cebrotea. @grangeryy, could you please assist with this? Thank you.

@cebrotea
Copy link
Author

looks like I will close this one as not reproducible for now. It is reproduced when using self-signed wildcard certificates. Thank you.

@cebrotea cebrotea closed this as not planned Won't fix, can't repro, duplicate, stale Jun 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Word Issue related to Word add-ins Needs: triage 🔍 New issue, needs PM on rotation to triage ASAP Type: product bug Bug in the Office Add-ins platform or Office JavaScript APIs
Projects
None yet
Development

No branches or pull requests

4 participants