FIX EIDSCA.AS04: Authentication Method - SMS - Use for sign-in.#1490
FIX EIDSCA.AS04: Authentication Method - SMS - Use for sign-in.#1490ThorNicolai wants to merge 2 commits intomaester365:mainfrom
Conversation
Treat includeTargets as an array and detect when the tenant setting is not explicitly set. Compute failingTargets where isUsableForSignIn != 'false', set tenantValue/testResult accordingly, and fetch directory objects to include display names for failing targets. Produce a clearer, detailed markdown summary listing each failing target and its isUsableForSignIn value and improve handling of the not-set case.
|
Thanks, @ThorNicolai! @Cloud-Architekt, is this something that will need to get fixed in the upstream EIDSCA project and then rebuilt here in Maester? |
|
Thanks for reaching out, @ThorNicolai! @SamErde, @ThorNicolai: Unfortunately, we can’t support that kind of advanced logic due to the EIDSCA schema and the simplified validation of Graph results. However, I’ve fixed the issue where multiple “false” outcomes caused the test to fail. Now, the check will fail only if at least one assigned group is permitted to use SMS for sign-in. I hope this improvement helps, even though it doesn’t yet indicate which specific group assignment triggered the failed test. |
|
Closing this one since we can now track in #1584 @ThorNicolai thank you so much for raising this and for proposing a fix. Very much appreciated! |
Description
User Bennell flagged an issue in discord related to multiple groups assigned to the SMS Authentication Method and this EIDSCA.AS04 test. The returned value would be 'False False' if for example 2 groups are assigned to the Authentication method SMS rather than 'False'. Marking the test as failed, where it would actually have passed if logic was set correctly.
Compute failingTargets where isUsableForSignIn != 'false', set tenantValue/testResult accordingly, and fetch directory objects to include display names for failing targets.
Contribution Checklist
Before submitting this PR, please confirm you have completed the following:
/powershell/tests/pester.ps1on your local system.