Prerequisites
ScubaGear Version
Main branch and all development branches in synch with main.
Operating System
Windows 11
PowerShell Version
5.1
M365 Environment and License(s)
Not environment specific.
🐛 Summary
New Entra policy checks (5.5, 5.6 and 5.7) dealing with better security for registered application credentials were introduced into ScubaGear. The functional tests for these new policies Fail when the tenant has app management policy data which creates the app_management_policies in the JSON. This is because the functional tests assume that the tenant only has data for the tenant-level default app policies. If there is data from the tenant that populates the app_management_policies JSON, the tests effectively get thrown off. The fix should be simple. Redesign the tests so that they account for the app_management_policies data.
Steps to reproduce
-
Go to the Enterprise Applications > Security > Application policies node and open Restrict max password lifetime
-
Select All applications with exclusions
-
Define a couple of excluded apps. For each app, set its max password lifetime to an expiration that exceeds the baseline compliant value.
-
Run the respective 5.x functional tests and observe the tests fail.
Expected behavior
The functional tests should work as expected regardless of the state of the tenant.
Output from Initialize-SCuBA (optional)
No response
Prerequisites
ScubaGear Version
Main branch and all development branches in synch with main.
Operating System
Windows 11
PowerShell Version
5.1
M365 Environment and License(s)
Not environment specific.
🐛 Summary
New Entra policy checks (5.5, 5.6 and 5.7) dealing with better security for registered application credentials were introduced into ScubaGear. The functional tests for these new policies Fail when the tenant has app management policy data which creates the app_management_policies in the JSON. This is because the functional tests assume that the tenant only has data for the tenant-level default app policies. If there is data from the tenant that populates the app_management_policies JSON, the tests effectively get thrown off. The fix should be simple. Redesign the tests so that they account for the app_management_policies data.
Steps to reproduce
Go to the Enterprise Applications > Security > Application policies node and open Restrict max password lifetime
Select All applications with exclusions
Define a couple of excluded apps. For each app, set its max password lifetime to an expiration that exceeds the baseline compliant value.
Run the respective 5.x functional tests and observe the tests fail.
Expected behavior
The functional tests should work as expected regardless of the state of the tenant.
Output from Initialize-SCuBA (optional)
No response