David Rowland:Thank you for the post.Can you confirm that one of the specific certificates we tested to be compatible is being used?If using one of the specific certificates listed in the article above, then could you confirm the certificate was issued as SHA-1 and not SHA-2?TSFalconFileMaker, Inc.
Thanks for your quick reply. I apologize for the delay, I wanted to test a few more things to gather more info.
Doh! What a simple oversight. We were using a Thawte certificate but a 'more secure' certificate (Thawte Web vs. Thawte SSL123 and both using SHA-1).
FMPro can connect to the databases with security enabled and Web is presenting the correct signed certificate.
Now, going forward we don't want to use the Thawte 123 certificate and will be looking at using an Extended Validation certificate as we do on our other sites. We also need to move to SHA2 for browser compatibility, especially given the announcements from Google. It sounds like until FMS is patched that we'll need to separate FMS and Web onto two separate hosts.
Thanks again for your help.
I have forwarded your request for FileMaker Server to support SHA-2 certificates. I also suggest you enter this into our Feature Requests web form at:
The entries into this web form populate a database file that is hosted and monitored by Product Management and Development. Although I could copy your post and paste it into the web form, there are a couple of questions asked on the form that only you can answer.