Efs Fmpro Login

[Tea Rochlitz]

Startingwith FileMaker Pro and Go 19.2.2 (released on March 16, 2021), the login dialog box only shows the configured OAuth Identity Providers (IdPs) for the server the File is hosted on. It will not show the usual username and password fields for native FileMaker accounts.

This does NOT depend on whether you are actually using externally authenticated accounts in the File you are opening. This behavior depends only on whether the server itself is configured to allow those OAuth IdPs. If any of the toggles as shown in the yellow highlight below are active, your 19.2.2 clients will be affected.

If you have configured a custom OAuth IdP as per our series of blog posts, then these toggles may be inactive. However, you will still get the same login dialog behavior with only the buttons for your custom IdP.

If that is not how you want things, hold down the shift key on Windows or option key on macOS when opening the File. This will force the traditional login dialog with the FileMaker account input fields.

As Claris continues to add more features and functionality to FileMaker, you have even more opportunities to strengthen and adapt your existing solution to do more for your business. If you need help adopting any new features, our team can help.

When a new employee will be using a previous team member's account for accessing aACE, the workstation used may cause difficulties. If that computer has stored the old login credentials, FileMaker will use this info to auto-login with the old account.

I'm having huge difficulty getting FileMaker Server 17 to work. The server operating system is Windows Server 2016. The client PC is Windows 10. The software installs OK but when I use FM Pro 17 client to connect remotely, I can't connect. I see the server under "Local Hosts" but when I click on the host name, after a minute or so I just get the message "connection failed".

Ports required to be open for LAN connectivity from Pro to Server are, unless I am mistaken, 80, 443 and 5003. When the Firewall is put back in, I know I will need these ports to be open. But as I say, even without, there is only a "failed connection" message.

I have installed FileMaker 16, 17, and 18 Pro on this client. All have the same issue, I have also tried switching the system firewall on and off, and giving privs to all 3 FileMaker versions while on.

Connect a known working client to the same network port and test. If that works, it must be something on the client. If the hardware on the known working client is similar, you could even swap harddisks so that you use the same mac address/computer. It is possible a switch causes issues, either with stored mac info, or with a layer 3 rule (if its a layer 3 switch).

Hello, I have a user with exactly the same issue today on Filemaker 16. He just had installed FM16 on his computer, can see the local server with "Bonjour", but can't connect "connection Failed" , Same with IP address or external IP address.

It wouldn't be an authentication issue unless you have FMS configured to use 'file list filtering' where it would first ask for credentials and only then show a list of files that the user has an account in. That's not the default setting though.

And even then, if the authentication through SSO failed (if you are using EA and SSO is possible in your setup) then FM would still show a login dialog and not the "connection failed". So this is either something on this user's computer (like the corrupted pems) or a networking issue.

On #2: just one account would do. If it doesn't work with a brand new account it would indicate that it is not something in the user's profile. Could still be something in the FMP installation; have you tried diffing the installed files vs the ones on a machine where it is working?

Other thing to try: move the machine to a different place in the network to rule out anything network-equipment related; switch from wifi to ethernet or vice versa depending on what is being used now. If both are active, disable one,...

Have you tried comparing packet captures with a working machine? That will tell you whether the faulty system is even trying to communicate with the server. Ideally you'd do this on the switch, but that depends what switch you have. Alternatively, run packet captures on both local machines (on a working one and on the broken one).

Probably the easiest way to check this would be to simply move the computer to another port, or better still, another switch. Having said that, it all depends on how the switches or switch stack is configured. Layer 3 switches add another layer of complexity. There are also switches that can be configured to dynamically manage perceived threats. In such a case, a power down won't help much. It all depends on what brand/model switch you have.

Issue Description/Details

I just want to jump in since this is the first active thread I've found on the topic. I am experiencing this issue and it is not isolated to one server. When selecting any host the 'Connection Failed' message is displayed immediately. I can connect to the same hosts using FMPA16/17 from the same machine.

I have experienced this issue previously when I installed both FMPA16 and FMPA17 and the resolution was unusual. I recall it being similar to adding an incompatible app to have accessibility access however despite confirming that no version of FMPA is in my accessibility list, I have tested this as a possible resolution.

Troubleshooting Performed

I have done a clean install with the most recent version of FMPA18 and it was a more up-to-date version; making it three versions where the issue persists.

The issue was also present in OSX High Sierra.

The rules in the firewall are identical for FMPA17/18 and the issue persists with the firewall disabled.

No third-party security software is in use.

Allowed FMPA18 to control the computer through 'Accessibility' in the 'Security & Privacy' settings.

Additional Information/Questions

Due to the issue being isolated to FMPA18 on a specific machine and previous experience I can rule out most of the usual suspects ie: server and network configuration.

Is anyone else experiencing the issue using a case-sensitive filesystem? I have had a wide variety of issues with applications that do not check if the filesystem is case-sensitive where the application is not designed to run on a case-sensitive filesystem. I doubt this is the case since this has happened with prior versions but I'm hoping for a common denominator that could be at the root of the issue at hand.

It would be immediately after I post regarding the issue that I stumble upon a resolution. I would like to apologize in advance if it is possible to update an existing post. It could be that I am new to the forums and unfamiliar with the interface or it could be that my previous post is awaiting moderator approval.

The Resolution

Copy the local certificates from a working installation of FileMaker Pro Advanced to the equivalent directory for the installation that cannot connect.

This resolution requires that the files can be obtained from one of the following sources, using the same license:

A working installation of a previous version of FileMaker Pro Advanced on the same system.

A working installation of FileMaker Pro Advanced on another system.

Filesystem Question/Update

In regards to my filesystem question from my previous post; this could be caused by a filesystem mis-match if the installer is looking for Server.pem and the package contains server.pem or vice versa. If anyone else experiencing this issue could please reply to this thread regarding their filesystem it would be much appreciated. If you are unsure, the filesystem can be viewed from 'Disk Utility':

Same thing happened to me on just one machine and simply copying the certificates over didn't fix the problem as FileMaker repeatedly overwrote root.pem with its own incomplete copy. Broken root.pem only contains a single certificate which belongs to FileMaker. Working root.pem contains a lot more certificates belonging to certification authorities. certifiedroot.pem will be completely missing as well.

We are using Acrobat Pro DC on several computers in our company (both Windows 7 and 10). We also use FileMaker (versions 14 and 15) which has container fields that we place pdf files into. FileMaker displays the pdfs in the container fields using a combination of Internet Explorer and the default pdf viewer (Acrobat in our case). Last week after the Windows and Adobe updates we started getting this error:

I fixed a Windows 7 PC by disabling the Adobe Reader add-on in Internet Explorer. However, the Adobe Reader add-on does not show up in any of the Add-on lists when I go to Manage Add-Ons in Internet Explorer 11 on a Windows 10 PC. I uninstalled Acrobat, ran a registry cleaner, then reinstalled an older version of Acrobat DC and the pdfs in container fields show up in FileMaker until Acrobat updates and the error message comes back.

I installed Adobe Reader in addition to Acrobat and the the reader add-on showed up in the Internet Explorer Manage Add-Ons list. I diabled the Reader add-on and now the pdf files will open from FileMaker. They don't show up in the container field of course, but the file opens in an instance of Acrobat. So its functional enough for our users to get their jobs done.

3a8082e126