putnam120/postgregent

A tool for monitoring and administering Postgres users/roles.

postgregent's Issues

Send RBAC Change Notifications

Configure Postgres to send at least one notification when a change is made to its collection of roles. These changes can be either creation, deletion, or modification of the role's attributes. The channel that is used should be easily tied to a regent.

Add ability to create permissions

Add the ability to create a new permission.

The new permission should be added to the database and known to the oracle.

Also properly handle errors.

React to Notification

The regent should react to notifications related to RBAC changes. For this issue the regent doesn't have to perform any reconciliation but should at a minimum indicate that the notification (and possible payload) was received.

Add ability to create roles and users

Track role usage

Add the capability to know the following details:

• which roles are used by a given permission
• which roles are used by a given user
• does a permission/role with a given name exist

Add ability to run queries in different databases

In managing permissions/roles/users sometimes it will be required to run queries in different databases. This is the case when trying to create a role in a database that's not the one currently connected to.

This can be accomplished through the use of dblink.

Improve search performance

The performance of searching to see if an RBAC asset with a given name exists can be improved.

Currently the search is done with RediSearch, but using RedisJSON would be better. The reason is that the key is uniquely determined by the asset name and asset type.

Disable the public role

On startup, the regent should remove all capabilities of the public role.

Create a Regent

Create a Regent that will connect to a Postgres cluster. Upon completion the Regent should remove the default capabilities of the public role.