-
Notifications
You must be signed in to change notification settings - Fork 20
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
OPIN0035 access control for op intents
- Loading branch information
Showing
16 changed files
with
700 additions
and
48 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
102 changes: 102 additions & 0 deletions
102
monitoring/uss_qualifier/scenarios/astm/utm/op_intent_access_control.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 |
---|---|---|
@@ -0,0 +1,102 @@ | ||
# ASTM F3548-21 UTM DSS Operational Intent Access Control test scenario | ||
|
||
## Overview | ||
|
||
This scenario ensures that a DSS will only let the owner of an operational intent modify it. | ||
|
||
## Resources | ||
|
||
### flight_intents | ||
|
||
A resources.flight_planning.FlightIntentsResource containing the flight intents to be used in this scenario: | ||
|
||
This scenario expects to find at least two non-conflicting flight intents in this resource. | ||
|
||
### dss | ||
|
||
A resources.astm.f3548.v21.DSSInstanceResource containing the DSS instance to test for this scenario. | ||
|
||
### second_utm_auth | ||
|
||
A resources.communications.AuthAdapterResource containing a second set of credentials for interacting with the DSS. | ||
|
||
Note that the 'sub' claim on the token that will be obtained for this resource MUST be different from the 'sub' claim on the token for the dss resource. | ||
|
||
### id_generator | ||
|
||
A resources.ineruss.IDGeneratorResource that will be used to generate the ID of the operational intent to be | ||
|
||
## Setup test case | ||
|
||
Makes sure that the DSS is in a clean and expected state before running the test, and that the passed resources work as required. | ||
|
||
The setup will create two separate operational intents: one for each set of the available credentials. | ||
|
||
### Ensure clean workspace test step | ||
|
||
#### Operational intents can be queried directly by their ID check | ||
|
||
If an existing operational intent cannot directly be queried by its ID, the DSS implementation is in violation of | ||
**[astm.f3548.v21.DSS0005](../../../requirements/astm/f3548/v21.md)**. | ||
|
||
#### Operational intents can be searched using valid credentials check | ||
|
||
A client with valid credentials should be allowed to search for operational intents in a given area. | ||
Otherwise, the DSS is not in compliance with **[astm.f3548.v21.DSS0005](../../../requirements/astm/f3548/v21.md)**. | ||
|
||
#### Operational intents can be deleted by their owner check | ||
|
||
If an existing operational intent cannot be deleted when providing the proper ID and OVN, the DSS implementation is in violation of | ||
**[astm.f3548.v21.DSS0005](../../../requirements/astm/f3548/v21.md)**. | ||
|
||
### Create operational intents with different credentials test step | ||
|
||
This test step ensures that an operation intent created with the main credentials is available for the main test case. | ||
|
||
To ensure that the second credentials are valid, it will also create an operational intent with those credentials. | ||
|
||
#### Can create an operational intent with valid credentials check | ||
|
||
If the DSS does not allow the creation of operation intents when the required parameters and credentials are provided, | ||
it is in violation of **[astm.f3548.v21.DSS0005](../../../requirements/astm/f3548/v21.md)**. | ||
|
||
#### Passed sets of credentials are different check | ||
|
||
This scenario requires two sets of credentials that have a diffrent 'sub' claim in order to validate that the | ||
DSS properly controls access to operational intents. | ||
|
||
## Attempt unauthorized flight intent modification test case | ||
|
||
This test case ensures that the DSS does not allow a caller to modify or delete operational intent that they did not create. | ||
|
||
### Attempt unauthorized flight intent modification test step | ||
|
||
This test step will attempt to modify the operational intent that was created using the configured `dss` resource, | ||
using the credentials provided in the `second_utm_auth` resource, and expect all such attempts to fail. | ||
|
||
#### Operational intents can be queried directly by their ID check | ||
|
||
If an existing operational intent cannot directly be queried by its ID, the DSS implementation is in violation of | ||
**[astm.f3548.v21.DSS0005](../../../requirements/astm/f3548/v21.md)**. | ||
|
||
#### Second credentials cannot modify operational intent created with main credentials check | ||
|
||
If an operational intent can be modified by a client which did not create it, the DSS implementation is | ||
in violation of **[astm.f3548.v21.OPIN0035](../../../requirements/astm/f3548/v21.md)**. | ||
|
||
#### Second credentials cannot delete operational intent created with main credentials check | ||
|
||
If an operational intent can be deleted by a client which did not create it, the DSS implementation is | ||
in violation of **[astm.f3548.v21.OPIN0035](../../../requirements/astm/f3548/v21.md)**. | ||
|
||
## Cleanup | ||
|
||
### Operational intents can be queried directly by their ID check | ||
|
||
If an existing operational intent cannot directly be queried by its ID, the DSS implementation is in violation of | ||
**[astm.f3548.v21.DSS0005](../../../requirements/astm/f3548/v21.md)**. | ||
|
||
### Operational intents can be deleted by their owner check | ||
|
||
If an existing operational intent cannot be deleted when providing the proper ID and OVN, the DSS implementation is in violation of | ||
**[astm.f3548.v21.DSS0005](../../../requirements/astm/f3548/v21.md)**. |
Oops, something went wrong.