User Login to FileMaker Server Admin ConsoleĪt MIT, when a FileMaker server is added to the domain, it has access to MIT's LDAP directory service, thereby allowing for Kerberos-based external authentication for compatible applications.The "Get a Single Record by ID", "Get Records", and "Find Records" endpoints now include an optional "dateFormats" parameter which controls the format of date and timestamp returned: 0 for US, 1 for file locale, or 2 for ISO8601.Īside from the above, the FileMaker Server 19.Data API Database Names endpoint guest control - The Database Names endpoint now requires authentication when the following items are both enabled: The Filter Database in Client Application option and the DenyGuestAndAutoLogin flag that can be set via the CLI.You will also see a few Data API in this release, including: Admin API login can now be authenticated with a JSON Web Token that can be revoked at any time from FileMaker Server.The Admin API can now get and set database filtering options.The Admin Console is now accessible even when the database server is stopped or down.In addition to the highlights above, this release brought a few more new features and updates to administer your databases: GET This needs only the header "Authorization: Bearer ". In the Admin API, users can both get the list of IPs currently allowed or update listed IPs, via the following commands: An important thing to note is that IP 127.0.0.1 (localhost) is always allowed and doesn't have to be specified by the user. In the Admin Console, this option can be found under "Administration > Restrict Access". In FileMaker Server 19.6, it is now possible to limit access to the Admin Console via the Console or the Admin API. Note that currently, Admin roles are limited to Admin Console sign-in and not the CLI or Admin API. Perform actions on schedules - Backup databases, Verify databases, Run scripts.Admin RolesĪlso introduced in this new release, Admin Roles allow you to administer a subset of databases using a distinct username and password with a chosen set of privileges. When checked, the database will be cloned to the specified folder or the default folder specified above. When creating a schedule, the Additional Settings menu now has the option to "Clone Only". This feature is also usable when creating backup schedules. If the destination parameter "-d" is not specified, the clone will be generated in the folder "FileMaker Server/Data/ClonesOnly/". As an example, the console command using this parameter would look like this:įmsadmin backup MyFile.fmp12 -d "filemac:/C:/M圜lones/" -cloneonly This parameter is used with the fmsadmin backup command to create an empty clone rather than a complete backup of the specified file. Admin Console and Admin APIįileMaker Server 19.6 brought many new additions to the Admin Console and Admin API, including the ability to limit Admin Console access to specified IP Addresses, access to the Admin Console even when the Database Server is stopped or down, and a new Admin command.Ī new Admin Console parameter has been introduced in the newest update, "-cloneonly". The second change is that newly created files will now have the "Show sign-in fields when OAuth is enabled" option enabled by default. First, Databases that aren't configured for OAuth will no longer show OAuth sign-in, even if FileMaker Server configurations contain OAuth settings. Additional OAuth ChangesįileMaker Server 19.6 also brings two other changes in OAuth. Documentation to get started can be found here. An Authkey must also be configured to properly set up Apple ID Sign-in. To use this, there are three prerequisites: an Apple Developer account, a valid SSL certificate, and SMTP configured on FileMaker Server to send email notifications. The highlight of this release! Users can now use their Apple ID to sign in to databases using OAuth.
0 Comments
Leave a Reply. |