Hi Dominik, thanks for providing those features. This is super useful and will help users to better organize their StreamPipes instance.
I will test start testing it once it is merged into dev. Philipp Am 09.11.21, 16:52 schrieb "Dominik Riemer" <[email protected]>: Hi, during the last weeks, I've worked on improved user management features for StreamPipes which are now ready to be merged into dev. Here's a summary of the changes, which I'm also currently adding to the docs: * The setup page is now obsolete - at initial startup, StreamPipes performs the installation in the background and adds a default user (User: [email protected], PW: admin). The default user can be overridden by providing * StreamPipes can be configured to allow self-registration and to allow users to restore their password. * StreamPipes can be configured to send emails (e.g., by pipeline elements through the API or client and by the system itself for password recovery or registration) * Users and groups can be managed and roles/privileges can be assigned to them * Individual permissions can be added for pipelines, dashboards, adapters and pipeline elements. Permissions can be changed by admins and are available in the overview section of each resource (e.g., pipeline overview and dashboard overview). * All requests from extensions service to the core are now authorized and made over the StreamPipes client. The runtimeContext of the wrappers includes a reference to the client pre-configured with default credentials. * The UI-core communication now relies on a standard token-based JWT authentication. I'll now merge this into dev and we'll fix some bugs in the upcoming weeks. It would be great if some of you can have a look and provide feedback. Some things might not yet fully work, but they hopefully bring us closer to a production-grade release 1.0. I'll also work on improving the documentation in the next weeks, so that we have a well-documented version for the upcoming release! Dominik
