Who Viewed the Topic
Hi. I just tried implementing OAuth using Google for FM16. When I set up my OAuth client ID on Google I stupidly put HTTPS instead of HTTP in the URL of our Filemaker server. So when I clicked on sign in with Google from FM I get an error 400 from Google.
So I went back to my Google Console and fixed the URL. Everything saved fine. But still when I click on sign in with Google from FM it tries to use the incorrect address with HTTPS. It's like it is cached in a preference somewhere and I don't know how to get rid of it. So far I have:
Restarted FMS Restarted the server Turned off Google under client authentication, restarted the server and started again. Tried a fresh install of FM Client on a different computer. Completely deleted my credentials in Google and started with a fresh client ID and done all the above again. Still it tries to use the wrong URL for my server. Although the URL has updated with my new client ID from Google.
I have ran out of ideas. Any help appreciated.
Internet plug-in adds new script steps and online help for FileMaker Pro 16.
Alphen aan den Rijn, Netherlands, June 26, 2017–Troi today announced the immediate availability of Troi URL Plug-in 5.0 for FileMaker Pro 16.
What is Troi URL Plug-in?
Troi URL Plug-in can help you fill in forms on the Internet, all from FileMaker Pro. It also retrieves data or images from web sites.
- use the POST command to fill in a web form and retrieve the result directly in FileMaker Pro
- use the GET command to retrieve data
- use the PUT command to to transfer files or upload data to web servers
- use the DELETE command to delete items on web servers
- use a secure connection (HTTPS) using SSL
- get access to password protected web pages, including those that require OAuth authorization
- get JPEG, PNG and GIF images directly into a container field
- specify cookies and proxy server settings
- send tweets to Twitter with ease!
What is new in version 5.0?
We rewrote Troi URL Plug-in for FileMaker 16 and it now has the following new functionality:
- Tested and made compatible with FileMaker Pro 16.
- Added new functionality to the TURL_Get function. When getting images, like jpegs the name of the image (like for example img_4321.jpg) is now also added to the container data.
- Fixed a problem with creating the correct OAuth signature for parameters in the TURL_SendAuthorizedRequest function.
- Fixed a problem with the TURL_SendAuthorizedRequest function for urls that contain extra parameters (after a question mark: like www.example.com?page=1).
- Made various minor changes to the example files to better work with FileMaker Pro 16.
- Updated the code by adding improved namespace handling to make the plug-in more robust.
Extra features when running FileMaker Pro 16
Version 5.0 adds the following new features when running in FileMaker 16:
- The URL Plug-in adds multiple script steps when running in FileMaker Pro 16. You can select these script steps in the script steps pane in Script Workspace, or you can begin typing the script step name, then choose the script step from the list that appears. The script steps significantly expand the possible actions you can perform with FileMaker Pro. Only steps that perform an action have been added as a script step. Functions that just return information (like for example TURL_GetLastHTTPStatusCode) are only available as an external function.
The following seven script steps are added:
- Delete URL
- Get URL
- Post URL
- Put URL
- Reinitialize URL Plug-in
- Send Authorization PIN URL
- Send Authorized Request URL
- Added new scripts to several example files, which demonstrate how to use the new external script steps of FileMaker Pro 16. The examples check if FileMaker Pro 16 is running and will select these new scripts.
- Added support for online help for the functions and script steps of the plug-in. You can now easily get online help from the Troi website, by clicking the Help button (the small question mark button) next to the function description in the functions pane or the script step description in the script steps pane.
Apart from these additions we fixed several bugs and made various further improvements. More detailed information on all changes and improvements implemented in Troi URL Plug-in 5.0 can be found at: https://www.troi.com/products/urlplugin/
Pricing & Availability
A fully functional demo version of Troi URL Plug-in 5.0 is available for downloading at: https://www.troi.com/products/urlplugin/
Licenses cost US$ 79 per user. Details on developer licenses and multi-user discounts can be found on our web site. You can order licenses from our web site.
Version 5.0 needs a new registration. The upgrade is free for users who bought a license for Troi URL Plug-in on or after May 24, 2016. Eligible users will be sent a new registration. Contact us if you have not received yours after June 30, 2017.
Upgrades from licenses bought before May 24, 2016 are available from US$ 49 per user. Upgrade prices for other licenses can be found on our web site. You can order upgrades from our web site.
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?
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.