Repository navigation
Fix Control Center action access in orchestration workers - #1759
Merged
Paul Lizer (paullizer) merged 1 commit intoOct 13, 2026
Merged
Paul Lizer (paullizer) merged 1 commit into
Paul Lizer (paullizer) merged 1 commit into
Conversation
Forward authenticated roles through action discovery and exact manifest resolution while preserving current access checks for preflight and retained results. Add worker-context and access-revocation regressions, document the fix, and bump the application patch version to 0.261.329. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Paul Lizer (paullizer)
merged commit Oct 13, 2026
b2c952e
into
paullizer-react-v2-ui
12 checks passed
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
integration_unavailable. Application Insights and App Service console logs identifiedexternal_source_preflight/selection_not_in_catalog.0.261.329.Linked issue
No associated issue. The user declined issue creation and requested the code fix, commit, push, and PR only.
Release Notes & Latest Features
Is this visible to end users?
Is this admin-facing (Admin Settings, governance, deployment, config)?
Should this become a Latest Feature card?
Screenshot needed for the card?
Release-note approval was requested but the user was unavailable. Optional release notes and issue creation were left out rather than expanding the requested scope.
Version bump
application/single_app/config.pyVERSIONthird segment bumped, or not needed because this is docs-onlydeployers/version.txtbumped, or not needed becausedeployers/was not changedApplication version:
0.261.328->0.261.329. No deployer files changed.Testing / validation
selection_not_in_catalogagainst the unfixed provider. The independent exact-resolution case reproducedintegration_access_denied, proving discovery alone was not a complete fix.3.1.3, Werkzeug3.1.6, and Semantic Kernel1.39.4. The initial system-Python attempt failed during collection because host pyOpenSSL25.3.0requires cryptography<47, but cryptography50.0.0was installed. The isolated environment used compatible cryptography46.0.7; no shared packages or repository dependency manifests were changed.python .\functional_tests\test_docs_app_surface_coverage.py— passed, 7/7 checks; the generated surface inventory remains current.python .\functional_tests\test_docs_site_quality.py— passed, 6/6 checks.git -c core.whitespace=blank-at-eol,blank-at-eof,space-before-tab,cr-at-eol diff --check— passed.git -c core.whitespace=blank-at-eol,blank-at-eof,space-before-tab,cr-at-eol diff --cached --check— passed.Documentation
Updated
CONTROL_CENTER_ACTION.mdandORCHESTRATION_EXTERNAL_SOURCE_ACCESS.md; addedCONTROL_CENTER_ORCHESTRATION_ROLE_PROPAGATION_FIX.mdwith the root cause, authorization boundaries, before/after behavior, and validation results.Security checklist
@swagger_route(security=get_auth_security())sanitize_settings_for_user()No new routes, frontend settings responses, browser assets, or credentials. Roles come only from the authenticated external-source identity; saved plans, saved runs, and ambient request roles cannot substitute for it.