Skip to content
This repository was archived by the owner on Sep 22, 2021. It is now read-only.
This repository was archived by the owner on Sep 22, 2021. It is now read-only.

Recommended approach to HTTP API Authentication? #22

@hhff

Description

@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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions