![]() 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 may mean that certain situations 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. Still in the Technologies section, under the Web Publishing heading, select No, do not enable web publishing, then click Next.Unless you plan to access your FileMaker database as a source via ODBC/JDBC, do not enable it. Note: Using a FileMaker database as a data source is not supported by IS&T at this time, but you may opt to enable this feature. In the Technologies section, under the ODBC/JDBC heading, select No, do not enable ODBC/JDBC.This information will be visible to the users of the database at the Open Remote File dialog and at the Admin Console Start page. In the Identification section, enter a Server Name, Server Description, and Administrator Contact Information for your server, then click Next.Warning: For security reasons, do not use your Kerberos credentials. The user name and password can be changed later through the Admin Console. In the Set Up Admin Console Account window, enter a User Name and Password for accessing the Admin Console, then click Next.Additional Security Settings: File Display Filter and SSL EncryptionĬlick on the thumbnails to view the full size images.Īfter installing FileMaker Server, you will be prompted to launch the Deployment Assistant.If you are uncertain of the process for setting up your server with the MIT recommendations, below is a step-by-step guide for configuring your server with our current recommended settings. Please follow all recommended MIT FileMaker Security Guidelines when setting up your server! ![]() Note: The above list does not include all necessary settings, but represents those for which IS&T has specific recommendations. Turn on SSL encryption and install a custom SSL certificate.Do not enable web publishing, unless you are setting up a dedicated server for this purpose.Do not enable ODBC/JDBC, unless you want FileMaker to be a data source for other applications.If you elect to run your own hosting environment, have secured it properly, and have experience with FileMaker Server, here is a reminder of the important recommended settings at MIT: IS&T recommends that IS&T-managed servers be used whenever possible for hosting FileMaker databases at MIT. In a changing computing landscape these recommendations in no way offer a guaranteed maintenance or risk-free hosting environment. The following web page offers MIT-specific configuration recommendations to help mitigate against security risks in the FileMaker hosting environment. Only experienced server administrators should attempt to do so, particularly where databases with sensitive data and/or mission critical functions will be housed. ![]() NOTE: IS&T recommends that IS&T Managed Servers be used for hosting FileMaker databases. ![]()
0 Comments
Leave a Reply. |