For SSL encryption to take effect, you must stop and restart your server software (Be mindful of users who might be impacted by doing so!):.To enable SSL encryption for communication between FM Server and FM clients, under Secure Connections, check the box for Require secure connections, then click Save.Check the option to List only the databases each user is authorized to access.In the Database Server pane, click the Security tab.In the left-hand column of the Admin Console, select Database Server.To limit who can see your hosted files through the Open Remote command and enable SSL Encryption: Result: The FileMaker Server Admin Console opens, and displays the Status section.Īdditional Security Settings: File Display Filter and SSL Encryption Result: The Deployment Summary is displayed. Select Edit Deployment in the Server menu in the Admin Console.To access the web publishing feature after you have installed FileMaker Server: Please consult the MIT FileMaker Security Guidelines and the ITAG Infrastructure Requirements for Applications and Systems. It is also best practice to not have any databases that contain sensitive data running on a FileMaker Server with web publishing enabled this means that certain situations may call for a 2-server setup. However, if you choose to utilize this feature, only non-sensitive data should be published to the web. IS&T does not provide Service Desk support for FileMaker web publishing. The user will not see either the web services or web publishing settings in the Admin Console unless the web publishing feature has been enabled through the Deployment Assistant. Note that enabling web services is not the same as enabling web publishing. In order for authorized server administrators to gain access to the Admin Console, web services must be turned on (this is done automatically by the FMS install process) and port 16000 must be open (this must be done manually). Note: FileMaker Server requires that web services be enabled on the server machine.
0 Comments
Leave a Reply. |