-
Notifications
You must be signed in to change notification settings - Fork 27
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
Add helpers to generate various authentication header types #4
Comments
Hey, just appedning "Username:Password" is not enough. You need to encode that as Base64. That was the missing part here. I am planning to make some updates to Fetch this week. I will make sure to do this too. |
Thank you! I would appreciate very much if you do this update. I bought you plugin because it's much more well documented than the other one on the marketplace. But only this issue is preventing me to achieve my goal. But actually, what is your plan to adress this issue? Do you intend to create a Base64 Encode node so we can manually encode our string before adding it to the array? Or something else? -Edit- The problem is: I was only able to encode the string to Base64 using a node from the competitor REST plugin. Now I will wait for Arunoda to create some solution to encode to Base64 on this plugin. It would be better to have everything needded on just one plugin. |
@juninholiveira I will create a simple helper function to add the username & password & it'll create the whole auth header. I will ping you when it's available on the marketplace. |
@arunoda Amazing! Better than what I imagined. I will wait patiently. |
@juninholiveira I just added support for this. Will available on the marketplace soon. |
Add support for:
The text was updated successfully, but these errors were encountered: