API key management about huginn HOT 8 CLOSED

To rehash what we discussed in IRC a little while ago:

• I think this is a good idea, since it's annoying to put the same oAuth credentials in three agents. Perhaps Huginn Users should have many Credentials that Agents can access?

from huginn.

That seems like the right way to go.  Should site-wide "app" credentials  be loaded from .env? If so, that may raise a few other questions:

1. What needs to happen if the app creds get reset?
2. Does an admin section get added to the UI for the sake of managing those keys?
3. Am I thinking way too far ahead for this discussion?

(By app credentials, I'm referring to when you "create an app" on Twitter, FB, et al. Example use case: rebranded Huginn instance wants its users' posts from Huginn to read "post at 5pm via myHuginn.")

On Fri, Aug 9, 2013 at 2:39 PM, Andrew Cantino [email protected]
wrote:

To rehash what we discussed in IRC a little while ago:

- I think this is a good idea, since it's annoying to put the same oAuth credentials in three agents. Perhaps Huginn Users should have many Credentials that Agents can access?

Reply to this email directly or view it on GitHub:
#76 (comment)

from huginn.

Perhaps instead of restricting it to just credentials there are other common configuration settings and things that can be shared between related agents.

In things like ifttt and zapier there's the concept of a "channel" and within a channel there are multiple "triggers". The channels are things like Facebook/Foursquare/Twitter/Dropbox whatever and the triggers are things like when something new is posted, or post something, etc.

The triggers seem to be like Huginn agents, and right now there's nothing in Huginn that's the equivalent of a channel.

While for the most part what would be shared between agents are things like OAuth keys and other credentials it's possible that other things could be shared. For example if there were a "travel" channel and other travel related agents beyond the current Adioso agent, it might make sense for them to share a common set of destinations of interest for example.

from huginn.

100% agree. Agents need some sort of container/categorization. I've been meaning to jot down some thoughts on this, but got distracted by life a few weeks ago. Putting it at the top of my list now.

On Fri, Aug 9, 2013 at 4:08 PM, Albert Sun [email protected]
wrote:

Perhaps instead of restricting it to just credentials there are other common configuration settings and things that can be shared between related agents.
In things like ifttt and zapier there's the concept of a "channel" and within a channel there are multiple "triggers". The channels are things like Facebook/Foursquare/Twitter/Dropbox whatever and the triggers are things like when something new is posted, or post something, etc.
The triggers seem to be like Huginn agents, and right now there's nothing in Huginn that's the equivalent of a channel.

While for the most part what would be shared between agents are things like OAuth keys and other credentials it's possible that other things could be shared. For example if there were a "travel" channel and other travel related agents beyond the current Adioso agent, it might make sense for them to share a common set of destinations of interest for example.

Reply to this email directly or view it on GitHub:
#76 (comment)

from huginn.

That's a nice Pattern! I'm currently looking at making what is known in IFTTT as a recipe. As Huginn allows multiple Triggers and Actions and lots of stuff in between, I have added a Scenario model that has_many :agents. A simple XML file defines multiple agents and their links, and I'm using vis.js to render individual scenario graphs rather than the current Google Charts API that blows up once the URL gets too long. My hope is to present the Scenario list as the main point of interaction rather than the current Agent list.

Unfortunately, I cannot easily share larger bits of code like the above without involving our corporate legal division 😒

from huginn.

Hey @KenYN, that's very much in line with my current thought process. I think it makes sense for Huginn to allow import and export of groups of Agents and their connections. A Scenario or Recipe would be a good name for this.

So you can't contribute any of your work back?

from huginn.

Related to #325 and #324, can probably be closed once we have those merged

from huginn.

Closing. We have Credentials and are fairly 12-factor. We could add a Liquid tag to access the ENV if needed.

from huginn.