dbTalk Databases Forums  

Script to access as user X

comp.databases.filemaker comp.databases.filemaker


Discuss Script to access as user X in the comp.databases.filemaker forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Andrea Crotti
 
Posts: n/a

Default Script to access as user X - 08-26-2011 , 03:38 AM






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...

Reply With Quote
  #2  
Old   
Bill
 
Posts: n/a

Default Re: Script to access as user X - 08-26-2011 , 07:59 AM






In article
<96daf825-389f-401d-b9a6-bace1d70d207 (AT) s20g2000yql (DOT) googlegroups.com>,
Andrea Crotti <andrea.crotti.0 (AT) gmail (DOT) com> wrote:

Quote:
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...
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.

Reply With Quote
  #3  
Old   
Andrea Crotti
 
Posts: n/a

Default Re: Script to access as user X - 08-26-2011 , 09:15 AM



On Aug 26, 2:59*pm, Bill <bbcoll... (AT) earthlink (DOT) net> wrote:

Quote:
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.

Reply With Quote
  #4  
Old   
Your Name
 
Posts: n/a

Default Re: Script to access as user X - 08-26-2011 , 04:26 PM



In article
<159b490f-6b19-4100-96de-90984d6e8241 (AT) o9g2000vbo (DOT) googlegroups.com>, Andrea
Crotti <andrea.crotti.0 (AT) gmail (DOT) com> wrote:

Quote:
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.
Oh, here we go again. Just because a product doesn't do what YOU want (or
more usually you can't find or work out how to do what you want), that
doesn't make it "idiotic". Every single thing ever created by man or
nature has "limitations". If you don't like FileMaker Pro, then there are
lots of other database products out there. \

As for security on FileMaker databases, Bill has given a good answer, but
the VERY FIRST thing you ever do is create a user account with FULL access
and make sure you keep the password safely recorded somewhere (or multiple
somewheres!). Even better, keep a backup copy of the datbase's structure
as a file with no security features. If you don't have a full accecss
account, you're going to end up recreating the entire database from
nothing again when you realise you need to change something.

Helpful Harry )

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.