Skip to content

Support single authentication method selection and validation metadata - #171

Open
pranems wants to merge 2 commits into
AzureAD:masterfrom
pranems:update-scim-auth-selection-20261021
Open

pranems wants to merge 2 commits into
AzureAD:masterfrom
pranems:update-scim-auth-selection-20261021

Conversation

@pranems

@pranems pranems commented Oct 21, 2026 •

Copy link
Copy Markdown

Summary

This PR adds single-method authentication validation and includes the bundle version and validation timing in SCIM onboarding results.

  • Authentication selection: The onboarding agent confirms either OAuth2ClientCredentials or FederatedIdentity and its connection parameters. The Logic App runs only the selected authentication test and requires it to pass. Existing semantic validation requirements, direct SCIM bearer usage and separately configured Entra provisioning credentials remain unchanged.
  • Version and timing: Bump the bundle from 13.0 to 14.0 and use VERSION as the single source for the deployed LogicAppVersion. Final results include the selected method, deployed version, validation start/completion UTC timestamps, Unix epoch seconds and elapsed whole seconds. These timestamps represent validation milestones, not the exact Azure run-history boundaries.

Deployment validates the generated version and deployed read-back, and rejects parameter-skip deployments that could retain stale metadata. Setup instructions, onboarding guidance and developer test documentation are updated.

Validation

  • All four authentication-selection regression tests pass from both the worktree root and the tests directory.
  • An OAuth-selected run completed with overall success: 20 successes, no failures or warnings, and five skips (four explicitly excluded Group tests and unselected federation).
  • An added regression test successfully exercised the FederatedIdentity-selected case.
  • With version and timing coverage included, all six local regression tests pass. Agent parameter-generation, JSON and whitespace checks also pass.

Commits

  1. Support single authentication method selection for SCIM onboarding
  2. Include bundle version and validation timing in SCIM results

Prashant Rane (ALLYIS INC) and others added 2 commits October 21, 2026 08:56
Adds an explicit choice between OAuth client credentials and Federated
identity for each SCIM onboarding validation run. The onboarding agent
confirms the selected method and its connection parameters, and the Logic
App runs only the corresponding authentication test. Requires the selected
test to pass, preserves existing semantic validation requirements, and
includes the selected method in final results. Direct SCIM bearer usage
and separately configured Entra provisioning credentials remain unchanged.

Updates shared parameters, authentication result aggregation, onboarding
instructions, setup documentation, and the validation overview. Adds
commented local regression tests with execution documentation and checks
version consistency against VERSION rather than a hard-coded release.
Bumps the Standard Logic App version to 14.0.

Validation: all four local regression tests pass from both the worktree
root and the tests directory. An OAuth - selected run,
completed with overall success, 20 successes, no failures or warnings, and five skips:
four explicitly excluded Group tests and unselected federation. And successful
added test successfully exercised the FederatedIdentity-Selected case..

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Use VERSION as the single source for the deployed LogicAppVersion.
Populate the runtime parameter during PowerShell and agent-led deployment,
leave the source template version blank, and include the deployed version
in the Orchestrator's native final results.

Capture validation start and completion timestamps once in existing
Orchestrator actions. Include their UTC values, Unix epoch seconds and
elapsed whole seconds in final results. These are validation milestones,
not the exact Azure run-history start and end timestamps.

Validate version preparation and deployed read-back, reject parameter-skip
deployments that could leave stale version metadata, and update setup,
agent and test documentation. Add offline deployment and timing regression
coverage without changing authentication or provisioning behavior.

Validation: six local regression tests pass. Agent parameter-generation,
JSON and whitespace checks pass.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@microsoft-github-policy-service

Copy link
Copy Markdown

pranems please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.

  1. Definitions.
    “Code” means the computer software code, whether in human-readable or machine-executable form,
    that is delivered by You to Microsoft under this Agreement.
    “Project” means any of the projects owned or managed by Microsoft and offered under a license
    approved by the Open Source Initiative (www.opensource.org).
    “Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
    Project, including but not limited to communication on electronic mailing lists, source code control
    systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
    discussing and improving that Project, but excluding communication that is conspicuously marked or
    otherwise designated in writing by You as “Not a Submission.”
    “Submission” means the Code and any other copyrightable material Submitted by You, including any
    associated comments and documentation.
  2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
    Project. This Agreement covers any and all Submissions that You, now or in the future (except as
    described in Section 4 below), Submit to any Project.
  3. Originality of Work. You represent that each of Your Submissions is entirely Your original work.
    Should You wish to Submit materials that are not Your original work, You may Submit them separately
    to the Project if You (a) retain all copyright and license information that was in the materials as You
    received them, (b) in the description accompanying Your Submission, include the phrase “Submission
    containing materials of a third party:” followed by the names of the third party and any licenses or other
    restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
    guidelines concerning Submissions.
  4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
    for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
    Submission is made in the course of Your work for an employer or Your employer has intellectual
    property rights in Your Submission by contract or applicable law, You must secure permission from Your
    employer to make the Submission before signing this Agreement. In that case, the term “You” in this
    Agreement will refer to You and the employer collectively. If You change employers in the future and
    desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
    and secure permission from the new employer before Submitting those Submissions.
  5. Licenses.
  • Copyright License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
    Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
    the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
    parties.
  • Patent License. You grant Microsoft, and those who receive the Submission directly or
    indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
    Your patent claims that are necessarily infringed by the Submission or the combination of the
    Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
    import or otherwise dispose of the Submission alone or with the Project.
  • Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
    No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
    granted by implication, exhaustion, estoppel or otherwise.
  1. Representations and Warranties. You represent that You are legally entitled to grant the above
    licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
    have disclosed under Section 3). You represent that You have secured permission from Your employer to
    make the Submission in cases where Your Submission is made in the course of Your work for Your
    employer or Your employer has intellectual property rights in Your Submission by contract or applicable
    law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
    have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
    You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
    REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
    EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
    PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
    NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
  2. Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
    You later become aware that would make Your representations in this Agreement inaccurate in any
    respect.
  3. Information about Submissions. You agree that contributions to Projects and information about
    contributions may be maintained indefinitely and disclosed publicly, including Your name and other
    information that You submit with Your Submission.
  4. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
    the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
    Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
    exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
    defenses of lack of personal jurisdiction and forum non-conveniens.
  5. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
    supersedes any and all prior agreements, understandings or communications, written or oral, between
    the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant