-
Notifications
You must be signed in to change notification settings - Fork 3
Feature/salesforce #4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Feature/salesforce #4
Conversation
Added Salesforce and updated to use PKCE Auth Code
PKCE support required adding NI SHA-256 function (LV 2020) and Base64URL encode VI Tested refresh_token support with Google API.
FYI. @pbrooks100 I published the base64 url update with OpenSerializer addon. I'll ask the annoying question: Can you port your changes to LV2013? It should prevent mass-compile of the entire project. It is difficult to diff/review with 600 files changed. I assume only 10-20 files are actually impacted by your changes. |
I'm using LabVIEW 2024 Community Edition; the earliest file version supported is 2017. I think my use of the LabVIEW native hash function caused one or two files to be save as 2020 (function added by NI in that version). |
@pbrooks100 I understand that I'm still clinging to very old version support. Again, thanks for these additions. I look forward to releasing them! |
Added Salesforce and updated to use PKCE Auth Code
PKCE support required adding NI SHA-256 function (LV 2020) and Base64URL encode VI Tested refresh_token support with Google API.
6fbe9c6
to
489ee09
Compare
After my first pass of just adding Salesforce, I found that I had broken other apps. I have now tested Google, Salesforce, LinkedIn, and GitHub with PKCE.
The web apps I created were all specifically created to test this library. The examples I submitted contain default client_id and client_secret values that are of no concern. I can also add up to 9 users for the Salesforce app (on request).