Hi Dominik,
thanks for providing the draft.
I’d like to discuss what the goals are that we want to achieve for the users.
I think there are two main functionalities we want to support:
1. What can a user do?
* Users have access to different StreamPipes features
* This effects the functionalities a user can use, e.g. one user can
only consume the dashboards while another user can create and edit pipelines.
* This basically effects all UI elements that are in the menu on the
left
* (e.g. CRUD pipelines, READ pipelines, CRUD adapters, READ adapters, …)
2. Who can see the data (adapters, pipelines, dashboards, …) of a user?
* With whom can a user share data?
* If a user creates an adapter / pipeline who can see this and who has
the rights to edit it?
For me the first point is quite clear, but I am not sure what the best way is
to achieve the second point.
Do we need another concept such as workspaces, projects or organizations?
I think the two simplest variants would be that a user only sees his own
pipelines or all users see everything from the other users, which is both not
ideal.
Philipp
> On 7. Oct 2021, at 18:54, Dominik Riemer <[email protected]> wrote:
>
> Hi all,
>
>
>
> I'm currently working on an improved authentication and authorization system
> for StreamPipes, so that users can be granted different access rights for
> the various features.
>
> While the authentication layer is straightforward, I'm thinking about the
> best approach to realize a good authorization system to meet our
> requirements.
>
>
>
> I've put a draft outline of the various options into the wiki at [1]. Do you
> have any ideas/wishes/comments on that? Glad to discuss the features in more
> detail.
>
>
>
> Cheers
>
> Dominik
>
>
>
> [1]
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191333349
>
>
>
>
>
>
>
