Just managed to successfully connect my SharePoint 2013 farm to an Office Web Apps 2013 farm using SSL! Woopidoo :)
Used the following articles:
http://technet.microsoft.com/en-us/library/jj219455.aspx
http://technet.microsoft.com/en-us/library/ff431687.aspx
I had issues tho (or else I would not write this post ;) )
When trying to connect SP to OWA, I kept getting this error:
New-SPWOPIBinding -ServerName kor-st-spowa01.kor.osl.basef
arm.net
WARNING: The server did not respond. Trying again (attempt 1 of 5).
WARNING: The server did not respond. Trying again (attempt 2 of 5).
WARNING: The server did not respond. Trying again (attempt 3 of 5).
WARNING: The server did not respond. Trying again (attempt 4 of 5).
WARNING: The server did not respond. Trying again (attempt 5 of 5).
New-SPWOPIBinding : Sorry, we have encountered an error and New-SPWOPIBinding h
as failed. If you are using a server configured with HTTP, you must include the
-AllowHTTP parameter.
At line:1 char:1
+ New-SPWOPIBinding -ServerName kor-st-spowa01.kor.osl.basefarm.net
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (Microsoft.Share...tNewWOPIBinding
:SPCmdletNewWOPIBinding) [New-SPWOPIBinding], SPCmdletException
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewWOPIB
inding
Browsing the ULS revealed the following:
Critical An operation failed because the following certificate has validation errors: Subject Name: CN=abc, O=abc, L=abc, C=abc Issuer Name: CN=DigiCert SHA2 High Assurance Server CA, OU=www.digicert.com, O=DigiCert Inc, C=US Thumbprint: abc Errors: PartialChain: A certificate chain could not be built to a trusted root authority. RevocationStatusUnknown: The revocation function was unable to check revocation for the certificate. OfflineRevocation: The revocation function was unable to check revocation because the revocation server was offline. .
EUREKA! Another lovely SSL issue.
Checking the certificate... seems fine! No errors in browser... hmmm..
Then I came to think about the revocation list and all the issues it brings to SharePoint.
Checked the policy setting just for the fun of it.
"Allow issuer certificate (AIA)" was not checcked due to "Define these policies" was not checked.
After checking both of them, i retested creating the WOPIbinding and voila - it worked! :) "Happy camper".
I just hope changing this setting won't cause any other SP issues later on...
