Skip to content

UI for API Key Pair Management#13225

Open
bernardodemarco wants to merge 1 commit into
apache:mainfrom
scclouds:api-keypair-ui
Open

UI for API Key Pair Management#13225
bernardodemarco wants to merge 1 commit into
apache:mainfrom
scclouds:api-keypair-ui

Conversation

@bernardodemarco
Copy link
Copy Markdown
Member

Description

PR #9504 restructured and extended the implementation of API key pairs to improve flexibility and security. It is now possible to create multiple key pairs per user, define a specific permission scope for each key pair and specify a validation period during which they remain active.

This PR exposes these new features in the ACS graphical interface. Among the new functionalities, users can now list all key pairs associated with a user, view their details and permissions, and register new key pairs with validity periods and permission sets.

Additionally, some minor fixes and enhancements were introduced to the API key pair backend workflows, including:

  • Default roles Domain Admin, Resource Admin and User were granted access to the listUserKeyRules API;
  • The type of the description column of the cloud.api_keypair table was changed from VARCHAR(100) to VARCHAR(1024); and,
  • The type of the description column of the cloud.api_keypair_permissions table is VARCHAR(255). However, the registerUserKeys API currently do not validate the size of the corresponding API parameter. This validation has been introduced.

Types of changes

  • Breaking change (fix or feature that would cause existing functionality to change)
  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Enhancement (improves an existing feature and functionality)
  • Cleanup (Code refactoring and cleanup, that may add test cases)
  • Build/CI
  • Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

  • Major
  • Minor

Screenshots (if appropriate):

2026-05-22.16-06-12.mp4

How Has This Been Tested?

The new UI sections were manually tested and their behavior was verified accordingly.

To test this patch, the backend must include PR #9504.

@codecov
Copy link
Copy Markdown

codecov Bot commented May 22, 2026

Codecov Report

❌ Patch coverage is 33.33333% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 18.09%. Comparing base (68221cf) to head (33e91bd).
⚠️ Report is 23 commits behind head on main.

Files with missing lines Patch % Lines
...ck/api/command/admin/user/RegisterUserKeysCmd.java 0.00% 2 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff              @@
##               main   #13225      +/-   ##
============================================
+ Coverage     18.08%   18.09%   +0.01%     
- Complexity    16718    16749      +31     
============================================
  Files          6037     6041       +4     
  Lines        542609   543106     +497     
  Branches      66432    66509      +77     
============================================
+ Hits          98136    98293     +157     
- Misses       433446   433764     +318     
- Partials      11027    11049      +22     
Flag Coverage Δ
uitests 3.50% <ø> (-0.02%) ⬇️
unittests 19.26% <33.33%> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@winterhazel
Copy link
Copy Markdown
Member

@blueorangutan ui

@blueorangutan
Copy link
Copy Markdown

@winterhazel a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

@blueorangutan
Copy link
Copy Markdown

UI build: ✔️
Live QA URL: https://qa.cloudstack.cloud/simulator/pr/13225 (QA-JID-940)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants