This PR enables support for using corald as an authenticated and rate-limited IPFS proxy server:
A new settings control lets use select whether they use the corald server, or a custom IPFS server
ipfs client code has been reworked to use different endpoints in corald case
ipfs client code includes the X-MyCoral-AccessToken header
The corresponding changes to corald and server-ops have been pushed and deployed, so the infrastructure is in place to start using this branch immediately.
KNOWN ISSUES:
Previously we were authenticating once and then storing the username forever without validating the token. Now each time a user interacts with IPFS, we are validating their auth token. If it expires or is invalid for any reason, we are showing a generic error. Instead we should kick them back to a login screen.
This PR enables support for using corald as an authenticated and rate-limited IPFS proxy server:
X-MyCoral-AccessTokenheaderThe corresponding changes to
coraldandserver-opshave been pushed and deployed, so the infrastructure is in place to start using this branch immediately.KNOWN ISSUES:
Previously we were authenticating once and then storing the username forever without validating the token. Now each time a user interacts with IPFS, we are validating their auth token. If it expires or is invalid for any reason, we are showing a generic error. Instead we should kick them back to a login screen.