I am trying to do a basic Insert from URL call with some CURL headers added and I keep getting authentication errors. This is the curl command sent by the provider for me to use.
curl -X GET --header 'Accept: application/json' --header 'api_key: 1234567890abcdefg' 'https://mydomain.leaddocket.com/api/endpoint' This is the curl I am setting up
-X GET \ --header 'Accept: application/json' \ --header 'api_key: 1234567890abcdefg' \ -trace $$curlTraceDump FM barks and says "Authentication Failed" but if I do this with the BaseElements plugin, it works just fine.
What I found when looking at the Curl Trace was that FM is dropping some of the headers I send and injecting its own. Here's the snippet I am finding from FM's trace:
GET /api/Leads/P endingExportIds HTTP/1.1 Host: mydomain.leaddocket.com User-Agent: FileMaker/16.0 Accept: */* Accept-Encoding: deflate, gzip Notice: both headers I sent were stripped and replaced.
Here is the response from BaseElements trace
GET /api/endpoint HTTP/1.1 Host: mydomain.leaddocket.com User-Agent: libcurl-agent-base-elements-plugin/3.3.4 Accept: application/json api_key: 1234567890abcdefg BE left my headers intact.
So what gives?
I'm looking for a method of authenticating with google via FileMaker. I would like to run post commands via the Insert from URL command to allow my FMDB to publish Cal Events to a specific calendar. Realistically I'd want this to be automatic when an appointment is assigned on the system.
At the moment, I can get a post to work, but it returns an error. I imagine this is because the authentication hasn't taken place.
Has anyone managed to get a working OAuth 2.0 setup/Google Login on Filemaker that will work with POST and GETs.
Once I've got Calendar to work, then I want to start on Drive and Gmail.
Good afternoon everyone,
When FMCloud was first announced, I was ecstatic; I'm all for moving towards cloud technology for my agency. I was nearly there...about to pull the trigger and start a migration scheme from my current setup into the FMCloud, but then the one big caveat was found..
"Supports custom app authentication via FileMaker user accounts only" AKA no External Authentication. But that is fine, I understand it was released for small businesses which need the scalability of AWS, but this DOES NOT work for my agency. I spent half a year moving away from filemaker user accounts, I can't go back; plus they have a Single Sign-on initiative that I'm trying to meet.
But I still need to get off of my old physical towers.So my next idea is that I want to spin up an EC2 in AWS and put filemaker server on it as an alternative, but I can't find any verbiage that details how that works(or if it works) in the way that I would like. Namely, I need my AWS server to talk to Active Directory, preferably by ADFS or SAML (lesser so).
So the question:
Can I setup external Authentication to an Active Directory from a server being hosted on AWS that is housing FileMaker Server 15? If so, What should I make note of before diving into this?
Thanks for any help and clarification someone can provide.
Hi all, running into an issue with Quicklook on Yosemite. When we run this script:
It causes Filemaker to open two instances of qlmanage, wait a while, then crash.
I've heard there are difficulties getting Quicklook to behave in Filemaker on Yosemite, so I began exploring other options.
I am aware of how to open a container file automatically using the computer's default settings for the file, but I was wondering if someone could help me understand how to open the contents of a container with Preview for OSX.
Thanks for any insight you can give!
SC 2.899 installation on OSX10.10 server and FMS 13.0v5 is giving a headache.
• closed WPE on FMSAT
• uninstalled previous version of SC
• Mac installer for SC2.899
• changed mod_proxy.conf according to documentation
• opened WPE on FMSAT
On the server, SC runs well when I check 127.0.0.1:16020/SuperContainer
From the client (LAN, no firewall), when I open http://serverIP/SuperContainerI get the message:
The requested URL was not found on this server. The link on the seems to be wrong or outdated. Please inform the author of about the error. If you entered the URL manually please check your spelling and try again.
This is the txt in the mod_proxy.conf file:
<Proxy *> Order deny,allow Allow from all </Proxy> ProxyPass /fmi ajp://127.0.0.1:16021/fmi ProxyPassReverse /fmi ajp://127.0.0.1:16021/fmi ProxyPass /fmwd_help ajp://127.0.0.1:16021/fmwd_help ProxyPassReverse /fmwd_help ajp://127.0.0.1:16021/fmwd_help ProxyPass /SuperContainer ajp://127.0.0.1:16021/SuperContainer ProxyPassReverse /SuperContainer ajp://127.0.0.1:16021/SuperContainer ProxyPass /SuperContainer http://127.0.0.1:16020/SuperContainer
ProxyPassReverse /SuperContainer http://127.0.0.1:16020/SuperContainer Am I missing something here?
Who Viewed the Topic