Skip to content

feat(CS): EC key support for global configuration #1262

feat(CS): EC key support for global configuration

feat(CS): EC key support for global configuration #1262

GitHub Actions / Central Server system test succeeded Nov 15, 2024 in 1s

124 passed, 0 failed and 0 skipped

Tests passed successfully

✅ src/central-server/admin-service/ui-system-test/build/test-results/systemTest/TEST-org.niis.xroad.cs.test.ui.CentralServerUiBehavioralTest.xml

124 tests were completed in 557s with 124 passed, 0 failed and 0 skipped.

Test suite Passed Failed Skipped Time
org.niis.xroad.cs.test.ui.CentralServerUiBehavioralTest 124✅ 557s

✅ org.niis.xroad.cs.test.ui.CentralServerUiBehavioralTest

✅ Central server repeat PIN field shows check-mark only when it matches with PIN prompt
✅ Submit enabled only when all fields are filled
✅ Example #1.1
✅ Example #1.2
✅ Example #1.3
✅ Central server is successfully initialized
✅ Correct password and username grant access
✅ Invalid password is rejected
✅ Invalid username is rejected
✅ Multiple member classes are created and present in the list
✅ Member Class description can be modified
✅ Member Class can be deleted
✅ Global group is added and listed
✅ Global group is added and listed
✅ System Parameters is present and can be edited
✅ API key creation wizard is working and key is created
✅ API key is created and revoked
✅ API key is created and edited
✅ User can only assign roles they have when creating/editing API key
✅ Member detail info is correctly shown
✅ Is able to change the name of the member
✅ Is able to delete the member and deleting the member requires the user to input the member code
✅ Search for member with long name
✅ The Subsystems table are correctly shown
✅ The subsystem can be added by code and the added subsystem immediately appears in the table
✅ Can be delete an unregistered subsystem
✅ Initial management services configuration is displayed
✅ Registering management service provider
✅ Member or subsystem cannot be added to server owner group
✅ Member and subsystem can be added to non owner group
✅ Added members are filter out from member candidates list
✅ User can filter member candidates
✅ Selection is preserved while filtering
✅ Group members can be deleted
✅ Add certification service
✅ Delete certification service
✅ View certification service details
✅ View and change certification service settings
✅ Add ACME certification service
✅ View and change acme certification service settings
✅ Intermediate CA can be added
✅ Intermediate CA list is correctly shown
✅ Intermediate CA can be delete in list
✅ Intermediate CA details can be viewed
✅ Intermediate CA OCSP responder can be added
✅ Intermediate CA OCSP responders list is correctly shown
✅ Intermediate CA OCSP responder can be edit in list
✅ Intermediate CA OCSP responder can be delete in list
✅ OCSP responder can be added
✅ OCSP responders list is correctly shown
✅ OCSP responder can be edit in list
✅ OCSP responder can be delete in list
✅ Add timestamping service
✅ Timestamping services list is correctly shown
✅ Timestamping service can be edit in list
✅ Timestamping service can be delete in list
✅ Add Key is disabled on logged-out token
✅ User can add only 2 signings keys after token log-in
✅ User can activate signing key
✅ User can't delete or activate signing key on logged out token
✅ User can delete signing key
✅ User logs out token and can not re-add signing key
✅ Add Key is disabled on logged-out token
✅ User can add only 2 signings keys after token log-in
✅ User can activate signing key
✅ User can't delete or activate signing key on logged out token
✅ User can delete signing key
✅ User logs out token and can not re-add signing key
✅ User can recreate anchor
✅ User can download anchor
✅ Anchor is updated if new signing key is added
✅ Anchor is updated if signing key is deleted
✅ User can recreate anchor
✅ User can download anchor
✅ Anchor is updated if new signing key is added
✅ Anchor is updated if signing key is deleted
✅ Example #1.1
✅ Example #1.1
✅ Example #1.1
✅ Example #1.2
✅ Example #1.1
✅ Example #1.2
✅ Example #1.1
✅ Example #1.2
✅ Example #1.3
✅ Example #1.1
✅ Example #1.2
✅ Example #1.3
✅ User can upload trusted anchor
✅ User can download trusted anchor
✅ User can delete trusted anchor
✅ Management Service TLS certificate is visible and all buttons are enabled
✅ Management Service TLS certificate can be viewed
✅ Management Service TLS certificate can be downloaded
✅ Management Service TLS key and certificate can be re-created
✅ Management Service TLS certificate sign request can be generated
✅ Management Service TLS certificate with different key can't be uploaded
✅ User Approves Management Request
✅ User Declines Management Request
✅ User views Details and Approves pending Management Request
✅ User views Details and Decline pending Management Request
✅ Verify sorting functionality in Management Requests table
✅ Search for pending Management Requests based on Free Text in Visible Columns
✅ Search for Management Requests based on Free Text in Visible Columns
✅ User Approves Management Request for additional authentication certificate
✅ User Approves Management Request for adding another security server
✅ User Approves Management Request for adding another client(subsystem) to security server
✅ User Approves Management Request for adding another client(member) to security server
✅ Management service provider can be registered
✅ Example #1.1
✅ User can change security server address
✅ User can delete security server
✅ Security server authentication certificates for "SS-X" are listed
✅ Security server clients can be sorted by subsystem
✅ Example #1.1
✅ Example #1.2
✅ Security server authentication certificates can be sorted
✅ Security server authentication certificate can be deleted
✅ Navigate from member details to Security Server details and back
✅ Member used servers are listed
✅ Configuration can be backed up and deleted
✅ Configuration backup can be downloaded and uploaded
✅ Already existing configuration backup is overwritten on upload
✅ Configuration can be restored from backup