![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
We want to add some security using filemaker PRO 11 and a few databases. So there are 3 or 4 files which should have different users, and I have to disable of course the automatic login as admin. It would be however to have a script on the different machines to open the files with the right users. In the script editor I didn't find anything useful anyway, is it possible somehow? An empty database with a script that open 3 or 4 files as user/ password would be perfect... |
#3
| |||
| |||
|
|
Accounts, passwords and privilege sets are set up on each FileMaker file separately. The user that wants to open a FileMaker file has to have an account name and password for that file. Automatic login should not be set up in any environment where multiple people could have access to the file. That is fundamental security. That is true whether the user opens the file directly, or through another file. Suppose File A is the first one open, and File A attempts to open File B. Then either: -The user must have the same account name & password with appropriate privileges on both files, or -File B will present a log-in dialog box on which the user puts his account name and password for File B. On a Mac, the keychain can store the account name and password for File B, so that when File A calls for File B, it will open based on the keychain. The Mac keychain is secure in that the user must log on to the Mac with the appropriate Mac account name and password in order to use that keychain. If the Mac keychain is to be used for this, the Mac should be set up to require login from sleep or screensaver, and the idle time allowed before going to sleep or screen saver should be short, so as to make it difficult for an unauthorized person to use the same account on the Mac if the authorized person leaves without logging of. I do not think there is a similar setup available for Windows, but I am not sure. Of course, your administrative procedures should tell users to close the database and log off their computer before they leave. Users must be conscious of security and act appropriately. Good administrative procedures and user training are essential. It is possible when using FileMaker Server to set up a system-wide access protocols, but AFAIK this is not available in FileMaker Pro. FileMaker comes with extensive documentation that includes information on security. The documentation is electronic, and is found in the file folder for FileMaker on your computer. Study this. There are also documents on the FileMaker web site related to file security. |
#4
| |||
| |||
|
|
On Aug 26, 2:59=A0pm, Bill <bbcoll... (AT) earthlink (DOT) net> wrote: Accounts, passwords and privilege sets are set up on each FileMaker file separately. The user that wants to open a FileMaker file has to have an account name and password for that file. Automatic login should not be set up in any environment where multiple people could have access to the file. That is fundamental security. That is true whether the user opens the file directly, or through another file. Suppose File A is the first one open, and File A attempts to open File B. Then either: -The user must have the same account name & password with appropriate privileges on both files, or -File B will present a log-in dialog box on which the user puts his account name and password for File B. On a Mac, the keychain can store the account name and password for File B, so that when File A calls for File B, it will open based on the keychain. The Mac keychain is secure in that the user must log on to the Mac with the appropriate Mac account name and password in order to use that keychain. If the Mac keychain is to be used for this, the Mac should be set up to require login from sleep or screensaver, and the idle time allowed before going to sleep or screen saver should be short, so as to make it difficult for an unauthorized person to use the same account on the Mac if the authorized person leaves without logging of. I do not think there is a similar setup available for Windows, but I am not sure. Of course, your administrative procedures should tell users to close the database and log off their computer before they leave. Users must be conscious of security and act appropriately. Good administrative procedures and user training are essential. It is possible when using FileMaker Server to set up a system-wide access protocols, but AFAIK this is not available in FileMaker Pro. FileMaker comes with extensive documentation that includes information on security. The documentation is electronic, and is found in the file folder for FileMaker on your computer. Study this. There are also documents on the FileMaker web site related to file security. Things have to be secure, but people also have to work well and quickly. Also ftp and other protocols didn't allow an automatic login, and then they invented expect or other technologies to bypass this idiotic limitation. Unfortunately as usual filemaker people just set some limitations for what they think is a good idea, course. |
\
)![]() |
| Thread Tools | |
| Display Modes | |
| |