Recommended approach to HTTP API Authentication?

[hhff]

Hi!

I've been working on understanding the pinning concept, which I understand to be highly important for keeping content available on the network "in a permanent manner".

We have a thread going here: https://discuss.ipfs.io/t/trying-to-better-understand-the-pinning-concept/754

Ultimately what I've realized is that content added via a local daemon can be pinned on a remote VPS IPFS node (therefore making the content "permanent while the node is up") via the official API described in this repo, but unfortunately there's no API auth built in here (yet?)

Potentially NGINX can handle the reverse proxy, and Authentication, allowing one to pin content remotely, but I'd like to know the recommended approach here?

[Kubuxu]

There is ipfs/kubo#1532 which is something we want to do in future but currently there isn't much of a recommended practice.

[hhff]

Cool - thanks @Kubuxu !

Do you see any reason why using NGINX for API Client Auth would be an issue?

http://nginx.org/en/docs/http/ngx_http_auth_request_module.html#auth_request
https://www.nginx.com/blog/authenticating-api-clients-jwt-nginx-plus/
https://github.com/auth0/nginx-jwt

[hsanjuan]

Closing this as this is an old issue and does not direclty belong to http api docs generation. If needed, please continue discussion in https://discuss.ipfs.io. Thanks!