 | |
#11
 
| |||
| |||
|
Re: Login issues -
11-05-2009
, 11:54 AM
|
Is there anyway to stop this kind of re-login scripts? Maybe, as other person suggests, using the scripps debugger but I think that the debugger will start working after the access is complete, am I right? |
script step, before it get to a relogin step.
I think you are still confusing the username with the account name.
User name is just the name set in app preferences and you can always
access this if you open FileMaker without actually opening your
database. The account name is what is actually paired with the password
for logging in to your database.
Feel free to send me a zipped copy of the database and known passwords
and I'll see if I can figure out what it's doing.
Howard
#12
| |||
| |||
|
|
On Nov 5, 2:18*am, Jokin <joaquin.casti... (AT) gmail (DOT) com> wrote: On 5 nov, 05:21, Grip <g... (AT) cybermesa (DOT) com> wrote: The meaning of "open the database using the parameter set in the server" for me is that even if I have full of diferent ways to enter to the databases, I never introduce any password, the client FM has the option when the databases are in a FM server to see which computer (username) is trying to open the database and just enter directly. This is a very good option when you have new people in your work and you do not want to create new usernames all the time in all the database. You can create a group with specific priviledges and then the new people is added to the group without changes in any database. I agree that I can not open the database locally if is open in a FMS. Anyway, I tried all the option, one it was to close it from the FMS and open locally, and again the "alive" database avoid all the process and decided to be opened as a Username without many priviledges. Regarding: You said in your post that files log into different accounts depending on the computer name. *That's pretty unsecure, because it means you're storing passwords in a script. And it's the likely cause of what you're experiencing. I dont agree, in fact, this is a wonderful and safe way to control the access through the server. Absolutely not. *All a client has to do to change their privileges is change the name of their machine. If someone can get onto your network then they can get any access they want. *If your files are accessible outside your local network, then anyone can do this. It may be convenient, but safe, no. I someone gets a hold of your physical file, they don't need a password cracker, they can pretty easily extract the passwords in other ways. Please be open-minded here and read up on FMP security. Yes, I have FMP advanced. As you know the debugger works when you are already in the database, however the problem is before I can check it with the script debugger. I think what is happening is the username and password are being auto entered by the machine's keychain system. *Then upon opening, a script changes the login to match the computer's name. Turn on the debugger. While opening the file, hold down the Shift (Windows) or the Option (Mac) key. Enter your admin password. You should now be logged in as admin and have the re-log script paused. *Cancel the opening script and you should be in. This approach assumes your admin user/pass is correct and the file is not already open by another file. I don't know much about your situation in general, but if you have 20 dbs, your either need to optimize your structure or you're running a good-size operation. *Either way, you really need to learn more about Filemaker Server and Filemaker Pro. |
recommendations using Shift and debugger. And, definitely agree with
Grip, I need to learn more about FMS.
Jokin
 |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.