You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to use the auto-updater to contact a custom server using authentication and bearer tokens, but it appears that there isn't an option for the generic server to pass http headers or any sort of authentication to a server. I looked into the source code and saw that it is possible to pass the http headers, but the libraries aren't exposed for usage in the generic server provider code or custom.
In researching this, I came across this post about custom providers #3261 which describes what I would like to, but there isn't any documentation on how to use it besides a comment to look at the test as an example.
Has anyone used the custom provider to pass http headers or authentication like I would like to do?
Could someone provide an example or update the documentation for usage of custom provider for auto-updater?
The text was updated successfully, but these errors were encountered:
electron-builder: 20.38.5
electron-updater: 4.0.14
Target: Windows_64
I am trying to use the auto-updater to contact a custom server using authentication and bearer tokens, but it appears that there isn't an option for the generic server to pass http headers or any sort of authentication to a server. I looked into the source code and saw that it is possible to pass the http headers, but the libraries aren't exposed for usage in the generic server provider code or custom.
In researching this, I came across this post about custom providers #3261 which describes what I would like to, but there isn't any documentation on how to use it besides a comment to look at the test as an example.
Has anyone used the custom provider to pass http headers or authentication like I would like to do?
Could someone provide an example or update the documentation for usage of custom provider for auto-updater?
The text was updated successfully, but these errors were encountered: