FileMaker 13 Server and Yosemite
We are setting up a new FileMaker 13 Server and just realized the FMS isn't comparable with Yosemite. Has anyone heard of a expected date that this will be fixed?
I was told 2-3 weeks when I inquired last week. Just a loose estimate, I guess.
TSFalcon - do you know any more specifics about the need to use a custom certificate for XML/PHP publishing? Is it still *possible* to enable XML/PHP on the server with the FileMaker provided built-in certificate?
And why the need for a custom one, as I would think the only difference would be the warning that happens due to the domain not matching the cert?
I want to know the reason do not enable XML/PHP publishing without a valid digital certificate, too. Is there any other reason?
Needless to say, using SSL/TLS is better.
And how about FileMaker WebDirect? We should not enable WebDirect without a valid digital certificate, too?
I'm confused by this talk of certificates. Could anyone please explain where to get one, and how to install it?
We all want to know why the default certificate doesn't have any security issue.
Downloaded FMS 13.5 last night got it all loaded on, then went to "Edit Deployment" under the "Server" Menu so I could turn on the web publishing and php support. Everything worked find until it went to the testing phase and it kept getting an error stating the connection test server was rejected. Bummer now what. I fiddled with it all night and they this morning I read somewhere that restarting the computer can solve this problem. Could it be that easy?! Yes it was, FileMaker Server 13.5 seems to running just fine on Yosemite.
Retrieving data ...