Add component-has-authentication-method Constraint

[Gabeblis]

Committer Notes

Purpose

This PR introduces a new constraint called component-has-authentication-method, which ensures that appropriate components dealing with leveraged systems, interconnections, and authorized services include the authentication-method property with a cardinality of 1 or greater.

Changes

Added Constraint:

• component-has-authentication-method: Validates that the authentication-method prop is present (cardinality >= 1) in components meeting any of the following criteria:
  • A system component with a leveraged-authorization-uuid property, representing a leveraged system.
  • A service component with an external implementation point and without a leveraged-authorization-uuid property, indicating a non-authorized service of a leveraged system or a service provided by an external system.
  • An interconnection component.
  • A service component with an internal implementation point and a direction property, indicating external connectivity.
  • A software component with an asset type of cli and a direction property indicating boundary communication.

Test Data

• Invalid Test Data File: Demonstrates cases where components meeting the above criteria are missing the authentication-method property.

• Valid Test Data File: Demonstrates successful cases where all relevant components include the authentication-method property.

Added YAML Files

• 2 YAML Files: Included pass and fail YAML files

All Submissions:

• Have you selected the correct base branch per Contributing guidance?
• Have you set "Allow edits and access to secrets by maintainers"?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you squashed any non-relevant commits and commit messages? [instructions]
• Have you added an explanation of what your changes do and why you'd like us to include them?
• If applicable, have all FedRAMP Documents Related to OSCAL Adoption affected by the changes in this issue have been updated.?
• If applicable, does this PR reference the issue it addresses and explain how it addresses the issue?

By submitting a pull request, you are agreeing to provide this contribution under the CC0 1.0 Universal public domain dedication.

[Gabeblis]

@wandmagic Any idea why the tests are failing here when they weren't yesterday?

[wandmagic]

@wandmagic Any idea why the tests are failing here when they weren't yesterday?

were they passing yesterday? it looks like a red X

[wandmagic]

   AssertionError: Positive test failed: Test failed with the following errors:
   component-has-authentication-method: invalid results received. 50% passing. Expected: pass_count "all", fail_count "none". Actual: 1 pass, 1 fail.

[Gabeblis]

   AssertionError: Positive test failed: Test failed with the following errors:
   component-has-authentication-method: invalid results received. 50% passing. Expected: pass_count "all", fail_count "none". Actual: 1 pass, 1 fail.

Yeah they all pass locally, and they passed yesterday. Nothing changed. Not sure why it says 50% now

[wandmagic]

   AssertionError: Positive test failed: Test failed with the following errors:
   component-has-authentication-method: invalid results received. 50% passing. Expected: pass_count "all", fail_count "none". Actual: 1 pass, 1 fail.

Yeah they all pass locally, and they passed yesterday. Nothing changed. Not sure why it says 50% now

that is odd, passes locally for me too!
i'll dig deeper into this it seems like an execution error

stale

[kyhu65867]

Looks good :)

[Rene2mt]

Looks good