Closed anju15bharti closed 3 months ago
coveralls
commented
3 months ago | Totals | |
|---|---|
| Change from base Build 10389490935: | 0.02% |
| Covered Lines: | 44449 |
| Relevant Lines: | 60012 |
HarshLunagariya
commented
3 months ago Description
Earlier, any user was able to drop user/role, irrespective of whether that user has required privileges or not.
With this commit, only dbo should have the permission to drop user/role.
Issues Resolved
BABEL-5173
Description Earlier, any user was able to drop user/role, irrespective of whether that user has required privileges or not.
With this commit, Only dbo and members of db_owner will have the permission to drop user/role. Additionally, this restricts dropping internal database principal such as dbo and db_owner, it restricts dropping non-Babelfish roles from TDS endpoint.
Issues Resolved BABEL-5173
Description
Earlier, any user was able to drop user/role, irrespective of whether that user has required privileges or not.
With this commit, only dbo should have the permission to drop user/role.
Issues Resolved
BABEL-5173
Test Scenarios Covered
Use case based -
Boundary conditions -
Arbitrary inputs -
Negative test cases -
Minor version upgrade tests -
Major version upgrade tests -
Performance tests -
Tooling impact -
Client tests -
Check List
By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.