You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Granting access to a table in a database that shares the name of a table in another database can fail
Revoking access to a table/database can fail if the AP UI postgres db and LF have got out of sync somehow (e.g. if permissions were already revoked in the LF console).
To Reproduce
Bug 1:
Grant access to a user to a table in a DB, then try to grant the user access to a table with the same name in a different DB.
Bug 2:
Grant user access to a table via the AP UI
Revoke access to the DB resource link in LF console
Revoke access to the table via AP UI. An error will appear but the user will no longer show as having access in the UI when navigating back to the table view
Grant access to the user again - this will appear to succeed, but the user will not have access in QS. Revoking access via the UI will error as above.
Expected Behaviour
Bug 1:
Users should be able to have access to tables that have the same name in different DB's
Bug 2:
Revoking and granting access should work and should result in access in Quicksight
Describe the bug.
Two bugs related to updating permissions:
To Reproduce
Bug 1:
Bug 2:
Expected Behaviour
Bug 1:
Bug 2:
Additional context
Sentry error related to Bug 2 https://ministryofjustice.sentry.io/issues/5856828705/?environment=production&project=4507447273324544&query=is%3Aunresolved+issue.priority%3A%5Bhigh%2C+medium%5D&referrer=issue-stream&statsPeriod=30d&stream_index=0
The text was updated successfully, but these errors were encountered: