RyanB

We are using a GoDaddy SSL.

Thanks. I have not worked through the document yet but I have discovered a possible cause. We use internal DNS in our office which points traffic to our FM Server FQDN to the LAN IP. Oauth is working fine outside the Office and if I edit my host record to resolve to the FMServer using the public IP Oauth works fine. This all worked before the upgrade. It makes no sense because DNS resolves fine internally and externally.

I thought that too and checked our firewall. Nothing should be getting blocked so I am not sure why it is stopped. Is FMS 19 using any new ports? I have never used https://oidcdebugger.com/ I am not sure what to put for Authorize URI (required), Response type (required) , or Response mode (required)

I was referring to the FM Login Window. No DNS names have changed. I will check out oidcdebugger. That might be just what I need. Thanks

We upgraded to FMS19 today and Google OAuth no longer works. The select an account screen comes up in a Browser, the redirect to our server is called and then there is no error and the DB is not logged in. It just leaves you at the login window. You could repeat this process over and over. If you reload the redirect URL you get an Authentication Failed error which I what I would expect if the authentication was failing. I think the original auth request is successful but does not open the DB. I also tested on another server with the same results.

Not sure if this is the correct area to post but my question is regarding security. Some of our databases are getting very big because of files and images stored in containers. We are thinking about setting up a process for storing files on our file server and reference them in Filemaker. We know how to do this but I can't seem to overcome a security issue. When accessing referenced files from a file server the user obviously has to have credentials to access the file server. We may have files from databases they do not have access to on the file server. How do we allow people to access referenced files without giving them access to other files that may be stored on the file server they don't have access to. I don't want to have to setup a folder with different credential for each database. I was thinking of just one big catchall folder. I don't want people to be able to leave FileMaker and just start browsing the mounted network drive. I was thinking of setting up a way to copy the referenced file to the temp path and open it from there. In this case I still think the network drive would need to be mounted. Any input would be appreciated.

I obviously wasn't clear enough in my first post. I did not intend to backup live FileMaker databases, or even unhosted filemaker backups for that matter, with TimeMachine. If all FileMaker Files were on a separate drive and Time Machine was only used for the OS why would that be a problem? I've been concerned about the performance hit that might come from RAID 1. Now I'm thinking in this scenario, I could Mirror or use TimeMachine to backup on the OS and keep the FileMaker files on a seperate drive (we don't have the money or resources for s higher level raid right now). The real problem has nothing to do with our FileMaker backups we backup often and follow the rules regarding the backup of live files. We have had drive issues in the past that have caused us to rebuild the server which has taken a lot of time. If I can have some redundancy or a quick way to restore back to an OS with a working FMServer, less the DBs, it will make disaster recovery easier and quicker. I hope this makes more sense. I know we can store the Filemaker Data where ever we want so I think it is a good idea to split it up. Ryan

We currently run FileMaker Server on a single drive on an Xserve, OS and Data. We backup our FileMaker DBs Internally Externally and Offsite. I am thinking of changing the configuration to a single drive with the OS and a RAID0 Mirror using the other two bays. The Mirror would contain only FileMaker data. Does anyone see anything wrong with using TimeMachine to backup the OS drive? I can't imagine it taking long or using a lot of resources since it won't be changing much. My thought is the data will be safe because we have multiple redundant copies plus the redundancy of the mirror. Then we can easily restore the OS drive if that fails from the TimeMachine backup and won't need to reconfigure our schedules as well as the tuning done in the OS. Thoughts? Thanks, Ryan