[SERVER-82311] Rename test tag not_allowed_with_security_token Created: 18/Oct/23 Updated: 14/Dec/23 Resolved: 14/Dec/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sophia Tan | Assignee: | Joseph Prince |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ntdi_nice_to_have, ntdi_test_plan | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Service Arch 2023-11-27, Service Arch 2023-12-11, Service Arch 2023-12-25 |
| Participants: |
| Description |
|
As we have introduced unsigned security token to replace `$tenant`, there are two kinds of security token now.
The test tag `not_allowed_with_security_token` actually only means the test has commands which are not allowed with signed security token. It is not related with unsigned security token. We need to rename the test tag to make it more explicit. |
| Comments |
| Comment by Githook User [ 14/Dec/23 ] |
|
Author: {'name': 'Joseph Prince', 'email': 'joseph.d.prince@me.com', 'username': 'josephdprince'}Message: GitOrigin-RevId: 598fb15a21c0c4e53ef47a4b5c5dc6f5ae5fd5ed |
| Comment by Sophia Tan [ 17/Nov/23 ] |
|
This test tag does not impact the correctness of the code. It's a nice to have task. We can do it later when we finish other high priority tasks. |