Repository navigation
Support single authentication method selection and validation metadata - #171
Merged
ggarima01 merged 2 commits intoOct 22, 2026
Merged
Conversation
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>
ggarima01
approved these changes
Oct 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds single-method authentication validation and includes the bundle version and validation timing in SCIM onboarding results.
OAuth2ClientCredentialsorFederatedIdentityand 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.VERSIONas the single source for the deployedLogicAppVersion. 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
Commits