For use with webhooks about fmrest.php

[kdoronzio]

Chris. Thanks. I believe you can post it to the project. I'm not sure if you need to be signed in as a contributor it not. If you prefer, it can't work out GitHub, you can email the changes to me. Thanks for offering. Ken

…

On Mon, May 13, 2019, 2:25 PM ChrisSLT ***@***.***> wrote: Hi, Thanks for this great php class. I've tweaked it to work with webhooks wherein it stores the session token to a text file on the server rather than a variable in the client's browser (since there wouldn't be a browser session in the case of webhooks). I'm new to Github - is this something you'd like me to post or share back to this repository in some way? Chris — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#6?email_source=notifications&email_token=AEKUF7EC23S5OXJO2WAY3XTPVGXCDA5CNFSM4HMSJZ4KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GTP3T3A>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEKUF7FMOFAFZARBOA2KUM3PVGXCDANCNFSM4HMSJZ4A> .

[ChrisSLT]

Thanks Ken, here it is. Again, thanks for kicking this off.

fmRestx is the class, and fmRestxExample is like your "Sample" file. If you put them both in your conf directory on a Filemaker server, you can set the variables into fmRestxExample, and you'll have a nice way to receive incoming webhooks and post to your Filemaker database.

Do you think the best way to handle tokens is by saving them to a file on the server, or is there a better way?

fmRESTx.txt
fmRestxExample.txt

[kdoronzio]

I didn't roll it into this revision because we were focusing on FM18 updates. I like the idea of having the option to store token information elsewhere. I need to roll this feature in carefully, though, to make sure that it can be turned on & off by the developer, without breaking the default cookie feature.

[ChrisSLT]

Great For Filemaker 18, are they still forcing us to get a token? It seems inefficient for a webhook to have to make that many calls

…

On Thu, May 23, 2019 at 1:40 PM kdoronzio ***@***.***> wrote: I didn't roll it into this revision because we were focusing on FM18 updates. I like the idea of having the option to store token information elsewhere. I need to roll this feature in carefully, though, to make sure that it can be turned on & off by the developer, without breaking the default cookie feature. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6?email_source=notifications&email_token=ACREQS7IUOJ3CR6X7S2VBTDPW3JJ5A5CNFSM4HMSJZ4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWC6V7Y#issuecomment-495315711>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACREQS5GBV64ZZ2FYBV2TOTPW3JJ5ANCNFSM4HMSJZ4A> .

[kdoronzio]

Yes, tokens are how FM Data API maintains security.

…

--------------------------------- Ken d'Oronzio Paradise Partners, Inc. 866-999-4006 x201

On Thu, May 23, 2019 at 5:05 PM Chris ***@***.***> wrote: Great For Filemaker 18, are they still forcing us to get a token? It seems inefficient for a webhook to have to make that many calls On Thu, May 23, 2019 at 1:40 PM kdoronzio ***@***.***> wrote: > I didn't roll it into this revision because we were focusing on FM18 > updates. I like the idea of having the option to store token information > elsewhere. I need to roll this feature in carefully, though, to make sure > that it can be turned on & off by the developer, without breaking the > default cookie feature. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > < #6?email_source=notifications&email_token=ACREQS7IUOJ3CR6X7S2VBTDPW3JJ5A5CNFSM4HMSJZ4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWC6V7Y#issuecomment-495315711 >, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/ACREQS5GBV64ZZ2FYBV2TOTPW3JJ5ANCNFSM4HMSJZ4A > > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#6?email_source=notifications&email_token=AEKUF7F7JAFM2XEG4JAZL7DPW4BIVA5CNFSM4HMSJZ4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWDPQUY#issuecomment-495384659>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEKUF7HK3LFECXMD7RNOPUTPW4BIVANCNFSM4HMSJZ4A> .

[ChrisSLT]

Yes, however I tend to see options in most other apis to be able to avoid token exchange for strictly server-side workflows. Hopefully one day with FM. Hope all is well, again, many thanks for the clarity/simplicity of your class, and let me know if I can help in any way.

…

On Thu, May 23, 2019, 5:54 PM kdoronzio ***@***.***> wrote: Yes, tokens are how FM Data API maintains security. --------------------------------- Ken d'Oronzio Paradise Partners, Inc. 866-999-4006 x201 On Thu, May 23, 2019 at 5:05 PM Chris ***@***.***> wrote: > Great > > For Filemaker 18, are they still forcing us to get a token? It seems > inefficient for a webhook to have to make that many calls > > > > On Thu, May 23, 2019 at 1:40 PM kdoronzio ***@***.***> > wrote: > > > I didn't roll it into this revision because we were focusing on FM18 > > updates. I like the idea of having the option to store token information > > elsewhere. I need to roll this feature in carefully, though, to make sure > > that it can be turned on & off by the developer, without breaking the > > default cookie feature. > > > > — > > You are receiving this because you authored the thread. > > Reply to this email directly, view it on GitHub > > < > #6?email_source=notifications&email_token=ACREQS7IUOJ3CR6X7S2VBTDPW3JJ5A5CNFSM4HMSJZ4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWC6V7Y#issuecomment-495315711 > >, > > or mute the thread > > < > https://github.com/notifications/unsubscribe-auth/ACREQS5GBV64ZZ2FYBV2TOTPW3JJ5ANCNFSM4HMSJZ4A > > > > . > > > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > < #6?email_source=notifications&email_token=AEKUF7F7JAFM2XEG4JAZL7DPW4BIVA5CNFSM4HMSJZ4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWDPQUY#issuecomment-495384659 >, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/AEKUF7HK3LFECXMD7RNOPUTPW4BIVANCNFSM4HMSJZ4A > > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6?email_source=notifications&email_token=ACREQSZJU25M5LPFJKK543DPW4HCRA5CNFSM4HMSJZ4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWDTBVY#issuecomment-495399127>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACREQSZAZBNMAAHP5MYJRJTPW4HCRANCNFSM4HMSJZ4A> .

[kdoronzio]

Our api wrapper certainly helps with that - in fact that's one of the reasons we created it - so you just pass the user name and password, and leave the token up to the api. I noticed in one of the edits you made (I think to "createRecord") that you commented out the login() line. That's fundamental to how the script works - it handles all the logins automatically and stores the token for you. By commenting out that step, you stop the auto-login feature.

…

--------------------------------- Ken d'Oronzio Paradise Partners, Inc. 866-999-4006 x201

On Thu, May 23, 2019 at 11:28 PM Chris ***@***.***> wrote: Yes, however I tend to see options in most other apis to be able to avoid token exchange for strictly server-side workflows. Hopefully one day with FM. Hope all is well, again, many thanks for the clarity/simplicity of your class, and let me know if I can help in any way. On Thu, May 23, 2019, 5:54 PM kdoronzio ***@***.***> wrote: > Yes, tokens are how FM Data API maintains security. > > > > --------------------------------- > Ken d'Oronzio > Paradise Partners, Inc. > 866-999-4006 x201 > > > On Thu, May 23, 2019 at 5:05 PM Chris ***@***.***> wrote: > > > Great > > > > For Filemaker 18, are they still forcing us to get a token? It seems > > inefficient for a webhook to have to make that many calls > > > > > > > > On Thu, May 23, 2019 at 1:40 PM kdoronzio ***@***.***> > > wrote: > > > > > I didn't roll it into this revision because we were focusing on FM18 > > > updates. I like the idea of having the option to store token > information > > > elsewhere. I need to roll this feature in carefully, though, to make > sure > > > that it can be turned on & off by the developer, without breaking the > > > default cookie feature. > > > > > > — > > > You are receiving this because you authored the thread. > > > Reply to this email directly, view it on GitHub > > > < > > > #6?email_source=notifications&email_token=ACREQS7IUOJ3CR6X7S2VBTDPW3JJ5A5CNFSM4HMSJZ4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWC6V7Y#issuecomment-495315711 > > >, > > > or mute the thread > > > < > > > https://github.com/notifications/unsubscribe-auth/ACREQS5GBV64ZZ2FYBV2TOTPW3JJ5ANCNFSM4HMSJZ4A > > > > > > . > > > > > > > — > > You are receiving this because you commented. > > Reply to this email directly, view it on GitHub > > < > #6?email_source=notifications&email_token=AEKUF7F7JAFM2XEG4JAZL7DPW4BIVA5CNFSM4HMSJZ4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWDPQUY#issuecomment-495384659 > >, > > or mute the thread > > < > https://github.com/notifications/unsubscribe-auth/AEKUF7HK3LFECXMD7RNOPUTPW4BIVANCNFSM4HMSJZ4A > > > > . > > > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > < #6?email_source=notifications&email_token=ACREQSZJU25M5LPFJKK543DPW4HCRA5CNFSM4HMSJZ4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWDTBVY#issuecomment-495399127 >, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/ACREQSZAZBNMAAHP5MYJRJTPW4HCRANCNFSM4HMSJZ4A > > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#6?email_source=notifications&email_token=AEKUF7FZAOE6FW7DYLWVNS3PW5OEFA5CNFSM4HMSJZ4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWEBYWQ#issuecomment-495459418>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEKUF7CSECINQI57U4EOLJLPW5OEFANCNFSM4HMSJZ4A> .

[ChrisSLT]

Hi - yes, I commented it out only because of storing the token in a text file. All the login function does is check for the existing of a token. Since after the first time it's used, there will always be a token in the text file, it seemed redundant. I think you're doing something cooler with storing it in a cookie, because it will automatically unset the token after 15 minutes, thus making auto login helpful. Wish there were some way to do that in a text file?

…

On Tue, May 28, 2019 at 7:09 PM kdoronzio ***@***.***> wrote: Our api wrapper certainly helps with that - in fact that's one of the reasons we created it - so you just pass the user name and password, and leave the token up to the api. I noticed in one of the edits you made (I think to "createRecord") that you commented out the login() line. That's fundamental to how the script works - it handles all the logins automatically and stores the token for you. By commenting out that step, you stop the auto-login feature. --------------------------------- Ken d'Oronzio Paradise Partners, Inc. 866-999-4006 x201 On Thu, May 23, 2019 at 11:28 PM Chris ***@***.***> wrote: > Yes, however I tend to see options in most other apis to be able to avoid > token exchange for strictly server-side workflows. Hopefully one day with > FM. > > Hope all is well, again, many thanks for the clarity/simplicity of your > class, and let me know if I can help in any way. > > On Thu, May 23, 2019, 5:54 PM kdoronzio ***@***.***> wrote: > > > Yes, tokens are how FM Data API maintains security. > > > > > > > > --------------------------------- > > Ken d'Oronzio > > Paradise Partners, Inc. > > 866-999-4006 x201 > > > > > > On Thu, May 23, 2019 at 5:05 PM Chris ***@***.***> wrote: > > > > > Great > > > > > > For Filemaker 18, are they still forcing us to get a token? It seems > > > inefficient for a webhook to have to make that many calls > > > > > > > > > > > > On Thu, May 23, 2019 at 1:40 PM kdoronzio ***@***.***> > > > wrote: > > > > > > > I didn't roll it into this revision because we were focusing on FM18 > > > > updates. I like the idea of having the option to store token > > information > > > > elsewhere. I need to roll this feature in carefully, though, to make > > sure > > > > that it can be turned on & off by the developer, without breaking the > > > > default cookie feature. > > > > > > > > — > > > > You are receiving this because you authored the thread. > > > > Reply to this email directly, view it on GitHub > > > > < > > > > > > #6?email_source=notifications&email_token=ACREQS7IUOJ3CR6X7S2VBTDPW3JJ5A5CNFSM4HMSJZ4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWC6V7Y#issuecomment-495315711 > > > >, > > > > or mute the thread > > > > < > > > > > > https://github.com/notifications/unsubscribe-auth/ACREQS5GBV64ZZ2FYBV2TOTPW3JJ5ANCNFSM4HMSJZ4A > > > > > > > > . > > > > > > > > > > — > > > You are receiving this because you commented. > > > Reply to this email directly, view it on GitHub > > > < > > > #6?email_source=notifications&email_token=AEKUF7F7JAFM2XEG4JAZL7DPW4BIVA5CNFSM4HMSJZ4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWDPQUY#issuecomment-495384659 > > >, > > > or mute the thread > > > < > > > https://github.com/notifications/unsubscribe-auth/AEKUF7HK3LFECXMD7RNOPUTPW4BIVANCNFSM4HMSJZ4A > > > > > > . > > > > > > > — > > You are receiving this because you authored the thread. > > Reply to this email directly, view it on GitHub > > < > #6?email_source=notifications&email_token=ACREQSZJU25M5LPFJKK543DPW4HCRA5CNFSM4HMSJZ4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWDTBVY#issuecomment-495399127 > >, > > or mute the thread > > < > https://github.com/notifications/unsubscribe-auth/ACREQSZAZBNMAAHP5MYJRJTPW4HCRANCNFSM4HMSJZ4A > > > > . > > > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > < #6?email_source=notifications&email_token=AEKUF7FZAOE6FW7DYLWVNS3PW5OEFA5CNFSM4HMSJZ4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWEBYWQ#issuecomment-495459418 >, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/AEKUF7CSECINQI57U4EOLJLPW5OEFANCNFSM4HMSJZ4A > > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6?email_source=notifications&email_token=ACREQSZH6T3K5YRMNGO6E3TPXW3TVA5CNFSM4HMSJZ4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWNWITI#issuecomment-496723021>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACREQSZ3U3K4LDNTVWYSCO3PXW3TVANCNFSM4HMSJZ4A> .

[kdoronzio]

Incorporating session storage in latest build, upcoming...