Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Default Account Name/Default Password not working FM9 Server

Featured Replies

Clients - FM 9.3

Host – FM9 Server 9.2

Platform – all Macs – all 10.4 (not panther or leopard)

This is a bit weird but I hope someone can help. I recently developed two virtually identical databases for a client (one essentially a copy of the other) both developed in FM9 V3 Advanced.

I built in four privilege sets in the Accounts and Privileges:

MasterOne – Full Access

MasterTwo – Full Access

Manager – Limited Access

User – Limited Access

The databases are set to use the User account on startup. FM Server authenticates using Filemaker accounts only.

Originally these were hosted without FM Server, just locally. Everything was fine.

I recently moved the databases to a Mac G4 Server using FM Server 9.2.

Now what happens when a user is opening the databases is that despite me setting the db to open automatically with the User account the Filemaker ‘Open’ dialogue box comes up as if the user is holding down the ‘Alt.’ Key. They aren’t.

Even stranger, when the user actually enters manually the User account name and password Filemaker says they do not have the access privileges to perform that operation! It gets worse. The only account that will work as a default is the MasterOne account. However, with one of the databases it returns the privileges that are actually set for MasterOne, on the other database (which is identical) it returns the privileges for the User Limited Access account!

I hasten to add that these databases work fine when they are standalone and open as instructed. It’s just on the server that they do this weird stuff.

I have deleted and re-created all the accounts. Performed all the things one would normally do in case of a corrupt file.

I believe I have set up the server software properly. I am at a loss on this. Anyone out there have any ideas?

First, upgrade the Server to 9.0v3, the latest v-rev.

Second, be sure that the fmapp Exteneded Privilege is set in the Privilege Sets attached to each of these Accounts. Otherwise, when hosted, they [color:red]will not open.

The auto-enter credentials feature requires both the Account Name and the password; be sure both are entered. This is not a particularly good practice in my view, inasmuch as it gives unchallenged access to the files. Once a user is admitted, there is a prospect of unauthorized privilege escalation.

Steven

  • Author

Thank you for this.

All the best.

David

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.