Skip to content

feat(m365): add onboarding auth method forms #8332

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

HugoPBrito
Copy link
Member

Context

Currently we have 2 auth methods (SP and SP+User) in the same form. This PR aims to introduce support for different onboarding flows in Microsoft 365 provider in separate forms.

Description

This PR implements logic to differentiate onboarding flows for M365 provider.

Checklist

API

  • Verify if API specs need to be regenerated.
  • Check if version updates are required (e.g., specs, Poetry, etc.).
  • Ensure new entries are added to CHANGELOG.md, if applicable.

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@HugoPBrito HugoPBrito requested a review from a team as a code owner July 21, 2025 08:40
@HugoPBrito HugoPBrito changed the title feat(m365): add onboarding auth method form feat(m365): add onboarding auth method forms Jul 21, 2025
Copy link
Contributor

github-actions bot commented Jul 21, 2025

⚠️ Changes detected in the following folders without a corresponding update to the CHANGELOG.md:

  • ui

Please add an entry to the corresponding CHANGELOG.md file to maintain a clear history of changes.

⚠️ Changes detected in the following folders without a corresponding update to the CHANGELOG.md:

  • api
  • ui

Please add an entry to the corresponding CHANGELOG.md file to maintain a clear history of changes.

⚠️ Changes detected in the following folders without a corresponding update to the CHANGELOG.md:

  • api
  • ui

Please add an entry to the corresponding CHANGELOG.md file to maintain a clear history of changes.

⚠️ Changes detected in the following folders without a corresponding update to the CHANGELOG.md:

  • api
  • ui

Please add an entry to the corresponding CHANGELOG.md file to maintain a clear history of changes.

⚠️ Changes detected in the following folders without a corresponding update to the CHANGELOG.md:

  • api
  • ui

Please add an entry to the corresponding CHANGELOG.md file to maintain a clear history of changes.

⚠️ Changes detected in the following folders without a corresponding update to the CHANGELOG.md:

  • api
  • ui

Please add an entry to the corresponding CHANGELOG.md file to maintain a clear history of changes.

⚠️ Changes detected in the following folders without a corresponding update to the CHANGELOG.md:

  • api
  • ui

Please add an entry to the corresponding CHANGELOG.md file to maintain a clear history of changes.

⚠️ Changes detected in the following folders without a corresponding update to the CHANGELOG.md:

  • api
  • ui

Please add an entry to the corresponding CHANGELOG.md file to maintain a clear history of changes.

⚠️ Changes detected in the following folders without a corresponding update to the CHANGELOG.md:

  • api
  • ui

Please add an entry to the corresponding CHANGELOG.md file to maintain a clear history of changes.

⚠️ Changes detected in the following folders without a corresponding update to the CHANGELOG.md:

  • api
  • ui

Please add an entry to the corresponding CHANGELOG.md file to maintain a clear history of changes.

⚠️ Changes detected in the following folders without a corresponding update to the CHANGELOG.md:

  • api
  • ui

Please add an entry to the corresponding CHANGELOG.md file to maintain a clear history of changes.

⚠️ Changes detected in the following folders without a corresponding update to the CHANGELOG.md:

  • api
  • ui

Please add an entry to the corresponding CHANGELOG.md file to maintain a clear history of changes.

⚠️ Changes detected in the following folders without a corresponding update to the CHANGELOG.md:

  • api
  • ui

Please add an entry to the corresponding CHANGELOG.md file to maintain a clear history of changes.

⚠️ Changes detected in the following folders without a corresponding update to the CHANGELOG.md:

  • api
  • ui

Please add an entry to the corresponding CHANGELOG.md file to maintain a clear history of changes.

⚠️ Changes detected in the following folders without a corresponding update to the CHANGELOG.md:

  • api
  • ui

Please add an entry to the corresponding CHANGELOG.md file to maintain a clear history of changes.

⚠️ Changes detected in the following folders without a corresponding update to the CHANGELOG.md:

  • api
  • ui
  • prowler

Please add an entry to the corresponding CHANGELOG.md file to maintain a clear history of changes.

⚠️ Changes detected in the following folders without a corresponding update to the CHANGELOG.md:

  • ui

Please add an entry to the corresponding CHANGELOG.md file to maintain a clear history of changes.

✅ All necessary CHANGELOG.md files have been updated. Great job! 🎉

✅ All necessary CHANGELOG.md files have been updated. Great job! 🎉

@HugoPBrito HugoPBrito requested review from a team as code owners July 21, 2025 08:42
Copy link

codecov bot commented Jul 21, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.94%. Comparing base (3892165) to head (625afc0).
Report is 32 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #8332      +/-   ##
==========================================
+ Coverage   88.08%   88.94%   +0.86%     
==========================================
  Files         897      192     -705     
  Lines       27645    15637   -12008     
==========================================
- Hits        24352    13909   -10443     
+ Misses       3293     1728    -1565     
Flag Coverage Δ
api 94.89% <ø> (?)
prowler 75.15% <ø> (-12.94%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
prowler 75.15% <ø> (-12.94%) ⬇️
api 94.89% <ø> (∅)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@HugoPBrito HugoPBrito force-pushed the PRWLR-7569-create-different-flows-of-onboarding-in-m-365 branch from 934f51a to ad9323a Compare July 21, 2025 13:41
Copy link
Member

@MrCloudSec MrCloudSec left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please, review my comments. Also, add the UI/API changelogs and put screenshots of the new changes in the description? Where are the changes of the API? Thanks.

@HugoPBrito HugoPBrito requested a review from a team as a code owner July 22, 2025 13:24
@HugoPBrito HugoPBrito force-pushed the PRWLR-7569-create-different-flows-of-onboarding-in-m-365 branch from c452838 to 638f44e Compare July 22, 2025 13:59
@HugoPBrito HugoPBrito removed request for a team July 22, 2025 14:00
{((searchParams.type === "aws" && searchParams.via === "credentials") ||
(searchParams.type === "gcp" && searchParams.via === "credentials") ||
(searchParams.type !== "aws" && searchParams.type !== "gcp")) && (
(searchParams.type === "m365" && searchParams.via === "credentials") ||
(searchParams.type === "m365" &&
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could you clarify what this is needed for and its purpose, please?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My intention was to add M365 to the group of providers that require a form to select the authentication method before showing the credentials form.

/>
)}
{providerType === "m365" &&
searchParamsObj.get("via") !== "service-principal-user" && (
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should avoid using this kind of condition (!==)

@paabloLC paabloLC added status/awaiting-reponse Waiting response from owner no-merge Please, DO NOT MERGE this PR. labels Jul 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/api component/ui no-merge Please, DO NOT MERGE this PR. status/awaiting-reponse Waiting response from owner
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants