18 FileMaker Pro Web Publishing Security Guidelines
3.
Select the privileges associated with this password.
4.
Click
Create
.
If a master password with full access has not already been defined, you must define one before
exiting this dialog box.
5.
Click
Done
.
Note
If the password limits browse privileges but does not limit the privilege to delete records, it is
possible for users to delete records they cannot view. If FileMaker Pro detects this situation, it will
display an alert when you create the password, but it will not prevent you from creating the password.
Tips for creating and maintaining passwords
When FileMaker Pro databases are used individually, shared on a peer to peer basis, or shared
using FileMaker Server, FileMaker Pro security consists of passwords and access privileges.
Passwords protect access to your databases, and the access privileges associated with those
passwords determine your guests ability to create, edit, delete, or export records, design layouts,
and so forth. This is a security model that is both simple and powerful.
The following are suggestions for creating secure passwords:
Secure passwords are typically more than eight characters in length, and include at least one
numeric digit.
Passwords are less secure when they include strings that are easily guessed, such as names
(especially the names of family and pets), birth dates, anniversary dates, and, in particular, the
words
password
,
default
,
master
,
admin
, and similar standard terms.
Change passwords frequently.
Use passwords only once.
If possible, assign a unique password for each user.
When creating a password for a Web published database or remote administration, use only a
combination of the characters A through Z, with at least one numeral. Do not include spaces, special
characters, or high ASCII characters in your password, as these may be interpreted incorrectly over
the Web.
If you are publishing the FileMaker Pro database over your intranet (such as a local area network
behind a firewall), you can assign any access privileges you may require for current users of the
database. You should consider creating more limited passwords for users who are accessing the
database via a web browser.
You will always need at least one master password if you are creating a group of passwords.
In addition, you and the users of your database should practice good management of known
passwords:
Do not record your passwords in a master file (especially if it is not, in turn, secured by a password
and encryption) or list.
Do not share passwords with other users; always go to the owner or administrator of a database
to obtain the correct password to be used.