On Mon, Nov 11, 2024 at 4:45 AM Wüthrich Daniel <daniel.wuethr...@lups.ch> wrote:
> Intern > > Intern > > Hi Nick > > > > Thank you. It seems that it was just a permission issue. When I assign > admin rights to the api-user all connections are displayed > > > > Is it correct, that there is no possibility for a "readonly" user? From a > security perspective, it makes little sense to use a user with full admin > rights for readonly calls. > > > In the current release, 1.5.5, access to the active connections requires admin-level credentials, either system admin credentials or admin credentials to the individual connections. In the upcoming 1.6.0 release, there is a new "AUDIT" permission that has been introduced at the system level that gives read-only access to login history and active connections, so that issue has already been addressed :-). -Nick >
