dkemme Posted May 31, 2005 Posted May 31, 2005 I have a three file solution, the first file uses the other two files but FMS hides them, cannot be seen from the open remote. Do I need to have these two hidden files password protected, or just the one file than can be seen? Would make keeping passnames/words simpler as only one file would need to be updated but as medical files need to be absolutely secure.
Walter B Posted May 31, 2005 Posted May 31, 2005 you could set the hidden files to automatically open with a set user name and password. Two reasons I'd consider a different option. One, if your main file becomes compromised, your two background files are also vulnerable. Two, potential audit trail issues. Depending on your solution and or industry, these could be very serious issues.
Vaughan Posted June 1, 2005 Posted June 1, 2005 All a solution's files should be defined with *exactly* the same passwords and access privileges. If they don't have the same passwords, the users may get prompted for a password each time one is required... and this is confusing, to say the least. The fact that the files are "hidden" on the server is immaterial: it's very easy to see them, just define a new relationship and you'll see all files on the server.
dkemme Posted June 1, 2005 Author Posted June 1, 2005 It gets a little difficult for the users, who are required to change passwords every 30 days, to do so for three files, remembering to enter the old password first and then the same new password three times in a row. I guess I should either use an external LDAP or script the changing of passwords. THANKS.
Vaughan Posted June 1, 2005 Posted June 1, 2005 Since you are using FMP7, combining att tables into a single file could simplify passwords greatly.
dkemme Posted June 1, 2005 Author Posted June 1, 2005 I have one data file with about 12 tables, one image file with one table but as 14 gbyte in size wish to keep separated as does not need to backed up every hour like the data file, and one file that is the front to the user for a separated model.
Walter B Posted June 1, 2005 Posted June 1, 2005 Have you considered authenticating externally against a domain server and using groups in your Filemaker solutions? You can then assign your user to the appropriate group on the domain directory for access and their password credentials are handled be the directory server. Your Filemaker solution wouldn't even need to be concerned with their passwords. Just a thought
dkemme Posted June 2, 2005 Author Posted June 2, 2005 I agree, an external domain directory would be best, I better start saving for OSX Server.
Recommended Posts
This topic is 7114 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now