1 of 2 people found this helpful
This is the exact same behavior filemaker pro has.
In WebDirect, if you want to link users to your solutions, just link them straight to it instead of the landing page:
If you want a custom landing page, make one with the links to your different databases using the above format.
FMP and FMPA are not used in this instance. Web Direct has changed in FMS 16, and I want to let Filemaker know about the issue. I do not want to give all my users a link or bookmark to multiple databases they use. I want FMS 16 to work as FMS 15 did. The user opens web direct and logs in with a username and password. As the feature I listed above is set, it shows the user a list of the databases they have access too. They click on the correct database and it opens. With FMS 16, they are required to put the same username and password twice. Also, if I ever changed the name of a database in FMS, the links or bookmarks would be broken. So, let's fix this issue and I'll use Mike's work around until it is corrected. Thanks
Thank you for your posts.
As "mikebeargie" mentioned (Thank you!), this was changed in FileMaker Server 16 for WebDirect to have consistency with FileMaker Pro 16.
If the aim was to have consistency between WebDirect and FileMaker Pro, surely it'd have been better to change FileMaker Pro to match WebDirect in this instance. If the user has already authenticated successfully once, it seems rather user-unfriendly to then request the same credentials again a moment later.
Do you know why this decision was made?
WebDirect is a lot newer than FileMaker, so parity would flow the other direction, towards how FileMaker has functioned for decades.
Also, Security has been a forward focus of FileMaker in recent years, so in their eyes the WebDirect system must have been less secure than what FileMaker Pro was using.
I wonder if some existing solutions would break in some way if they changed this behaviour with the full FileMaker Pro client. If that were the case I can see why that might've been done - but otherwise it seems a retrograde step. Would love to know what FileMaker, Inc's "official" line on this is.
What databases do they not have access to? Why would you change a file name?
FM16 prohibits shared hosting of client file or mixing your development files with client files.
FMP can store the server login in the keychain, but WD needs two logins. It makes sense. It is more secure. I can see situations where this is desireable.
Using OAuth authentication makes this more bearable as it is just a click to verify.
Another more obscure issue that this behavior change solved is the ability to open a database with different credentials from the ones entered for File Display Filter. E.g. if I enter an account with very generic privileges at FDF challenge (e.g. to see all public-facing databases), but then want to open a particular one in that list with more powerful privileges, I can now do that (by entering different account at 2nd challenge). Whereas in 15 WebDirect, that was not possible. You always opened file with FDF credentials (even trick of holding down Alt/Opt key while clicking on database in launch center (which works to force login dialog in WebD when auto-login acct has been specified in database File Options) did not work to bring up second login dialog after FDF authentication in 15).
I sort of 'get' the reasoning but I still put it into the category of 'annoyance', as it seems to wander too far away from Apple Design Guidelines: Authentication - User Interaction - Human Interface Guidelines for macOS Apps
I think it is a little bit of a hassle but not too bad. I am still trying to understand how so many people have this as an issue. You have the option to hide the file from displaying at all and the option to filter.
Why is this being used to obscure files in production? I can think of only a couple of reasons that are not likely common. I use this on my development/demo server. Clients understand that there will be two logins. Why would this filtering be used on a clients server?