Backport #10273 to 4.20: Grant access to 2FA APIs for default read-only and support roles#10702
Conversation
|
@blueorangutan package |
|
@bernardodemarco a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## 4.20 #10702 +/- ##
============================================
- Coverage 16.01% 16.01% -0.01%
Complexity 13112 13112
============================================
Files 5652 5652
Lines 495840 495840
Branches 60045 60045
============================================
- Hits 79414 79410 -4
- Misses 407566 407568 +2
- Partials 8860 8862 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 13032 |
DaanHoogland
left a comment
There was a problem hiding this comment.
we need to see if a potential 4.19.3 will also suffer such issues.
I don't think it will. Since the SQL queries are included in the Also, when such environments get upgraded to a version greater than |
|
@blueorangutan test |
|
@DaanHoogland a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
|
[SF] Trillian test result (tid-12984)
|
|
[SF] Trillian test result (tid-12991)
|
|
merging this , trusting it has been tested functionaly (see #10273 (review)) |
Description
The PR #10273 granted access to 2FA-related APIs for the following roles:
Read-Only User - Default,Support User - Default,Read-Only Admin - Default, andSupport Admin - Default. It was targeted at the4.19branch and, as such, the corresponding SQL changes were added to theschema-41910to41920.sqlfile:cloudstack/engine/schema/src/main/resources/META-INF/db/schema-41910to41920.sql
Lines 25 to 45 in d32065f
When the patch was merged (January 30, 2025), version
4.20.0.0had already been released (December 2, 2024). Therefore, it's necessary to backport the #10273 changes to the4.20branch and include the SQL updates in theschema-42000to42010.sqldatabase upgrade file.Thus, this ensures that environments currently running version
4.20.0.0will receive the changes when upgrading to a next release (i.e.,4.20.1).Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?