forked from spiffe/spire
-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Marcos Yacob <[email protected]>
- Loading branch information
Showing
1 changed file
with
6 additions
and
6 deletions.
There are no files selected for viewing
12 changes: 6 additions & 6 deletions
12
test/integration/suites/force-rotation-jwt-authority/README.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,12 @@ | ||
# Force rotation with Upstream Authority Test Suite | ||
# Force rotation with JWT Authority Test Suite | ||
|
||
## Description | ||
|
||
This test suite configures a disk-based Upstream Authority to validate the forced rotation and revocation of X.509 authorities. | ||
This test suite configures a single SPIRE Server and Agent to validate the forced rotation and revocation of JWT authorities. | ||
|
||
## Test steps | ||
|
||
1. **Prepare a new X.509 authority**: Verify that a new X.509 authority is successfully created. | ||
2. **Activate the new X.509 authority**: Ensure that the new X.509 authority becomes the active authority. | ||
3. **Taint the old X.509 authority**: Confirm that the old X.509 authority is marked as tainted, and verify that the taint instruction is propagated to the agent, triggering the rotation of all X.509 SVIDs. | ||
4. **Revoke the tainted X.509 authority**: Validate that the revocation instruction is propagated to the agent and that all the SVIDs have the revoked authority removed. | ||
1. **Prepare a new JWT authority**: Verify that a new JWT authority is successfully created. | ||
2. **Activate the new JWT authority**: Ensure that the new JWT authority becomes the active authority. | ||
3. **Taint the old JWT authority**: Confirm that the old JWT authority is marked as tainted, and verify that the taint instruction is propagated to the agent, triggering the deletion of any JWT-SVID signed by tainted authority. | ||
4. **Revoke the tainted JWT authority**: Validate that the revocation instruction is propagated to the agent and that all the JWT-SVIDs have the revoked authority removed. |