Consider other auth types than bearer token for API and security considerations

[yaelberger-commits]

Description

As a (user), I need to be able to do (X) so that I can achieve (Y) outcome.

WHY are we building?
WHAT are we building?
VALUE created by our solution

https://cds-snc.freshdesk.com/a/tickets/20651

Documentation and Artifacts

Good docs, figma mockups, ADRs, screenshots etc.

Acceptance Criteria

Given some context, when (X) action occurs, then (Y) outcome is achieved

• Cypress UI tests if needed.
• Generate appropriate log messages so that executions of this feature can be tracked
• Can misuse of this feature cause harm? If yes, create an alert
• Update the status of related findings, insights, and hypotheses on the Research Airtable
• Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)
• Does the feature change our Information Architecture? If so, update the Sitemap in En/Fr

• A11y
• Bilingualism
• Privacy considerations
• Security controls in place
• Measuring success and metrics

Related Research Airtable records

• (find stuff yourself)

QA Steps

• Tested in a realistic production scenario