This happened this am to our solution as well. ???
Odd... anything to do on filemaker's end?
I haven't done anything with this information yet, but I figured I would pass it along. I'll let you know how we make out ...
Security Update - FileMaker 13.0v9/FileMaker 12
Answer ID: 14358
Available for: FileMaker 13 and FileMaker 12 product lines.
Impact: A potential SSL issue could allow network communication to be compromised.
Description: An issue with FileMaker's root SSL certificates could allow network communication to be compromised. This issue was addressed by updates to application UI and to FileMaker security certificates.
Thanks, if you have any update please let me know. I have forwarded this issue to our network administrator.
As a temporary solution, we turned off SSL ...
(located in the FileMaker Server Admin Console > )
This is by no means the "right" way, but it got us up and running again - nothing in our DBs is sensitive.
The instructions on the link above seem to be the way to go - but to be honest, it's a little complicated and above my pay grade.
Thank you for the posts.
If FileMaker’s default SSL certificate is being used by FileMaker Server 12 (Advanced) unpatched or FileMaker Server 13 and the FileMaker Server has not been updated to version 9, and a client with version 9 of FileMaker Pro 13.0v9 (Advanced), FileMaker Go 13.0v9, or FileMaker Pro 12 (Advanced) unpatched attempts to connect, then this is the error which will be received:
“The file, test could not be opened. The SSL certificate for FileMaker Server is not compatible with this FileMaker client.
Contact your sever administrator.”
In order to not get the error, the FileMaker Server 13 should be updated to version 9 and FileMaker Server 12 (Advanced) should be patched.
For more information, please review the following knowledge base articles: