I suggest you ...

Read API key for a single private feed

In our enterprise we have multiple feeds that we want to keep strictly separated from each other. However, when creating a new API key the read functionality is always on all available feeds by default.

As we use these keys throughout our automation pipeline we do not want to handout a single key with read permissions on all our feeds. A possible workaround could be to create a user for each feed, provide that user with 'Can consume this feed' rights and use the API key from that user. But that's just not even viable to maintain.

I'm sure I'm not the first one to comment on the read all implementation. What's the proposed way to handle this, or can the feature to scope read permissions to a single feed be implemented?

9 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Jasper Cottenie shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base