search

ElementsProject / lightning-charge

A simple drop-in solution for accepting lightning payments
MIT License
554 stars 80 forks source link

Multiple API keys #44

Closed BartKnucle closed 6 years ago

BartKnucle commented 6 years ago

Hi,

I would like to know if there is a plain (or if it is possible?) to create multiple api keys without runnning multiple charged instances?

Thank you!

shesek commented 6 years ago

Currently, each charged instance has a single API key associated with it.

What would you want to use multiple API keys for? Different c-lightning backends for each? Or the same backend, but isolate their access to the invoices they created? Or something else?

BartKnucle commented 6 years ago

Yes, the second option. I wanna be able to expose differents api key to multiple woo commerce merchants for example without having to run multiple instances of c-lightning or charged.

shesek commented 6 years ago

So basically, a Strike-like hosted solution for processing lightning payments?

This would be an interesting use-case indeed, but it is currently not possible. I don't have any specifics plans to implement this, but I think that Lightning Charge could be a great starting point for doing this.

This could possibly even be implemented as a separate daemon that sits on top Lightning Charge, that manages authentication and exposes a similar API, so that you won't have to maintain a fork and can keep pulling upstream changes.

I'm closing the issue, but feel free to comment if you have more questions.

BartKnucle commented 6 years ago

Thank you! I'll explore your third layer solution ;)