Revert serviceUrl allowlist (ADO 5310460)#415
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Reverts the (unshipped) serviceUrl hostname allowlist defense-in-depth feature from the Teams Apps SDK before public release, removing the related public configuration surface and tests while keeping other token-validation hardening (scope/issuer handling) intact.
Changes:
- Removes
additional_allowed_domainsfrom app options and stops plumbing it throughApp→HttpServer→TokenValidator. - Deletes serviceUrl hostname allowlist logic (helper + enforcement in
HttpServerandTokenValidator) and the associated cloud preset data. - Removes allowlist-focused unit tests in
packages/apps/tests.
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| packages/apps/tests/test_token_validator.py | Removes serviceUrl allowlist and additional_allowed_domains token validator tests. |
| packages/apps/tests/test_http_server.py | Removes serviceUrl allowlist request-handling tests and initialization plumbing assertion. |
| packages/apps/src/microsoft_teams/apps/options.py | Removes additional_allowed_domains from AppOptions / InternalAppOptions. |
| packages/apps/src/microsoft_teams/apps/http/http_server.py | Removes allowlist configuration + enforcement in request handling and initialization. |
| packages/apps/src/microsoft_teams/apps/auth/token_validator.py | Deletes allowlist helper + domain enforcement; leaves serviceUrl claim equality validation. |
| packages/apps/src/microsoft_teams/apps/app.py | Removes forwarding of additional_allowed_domains into server/token-validator setup. |
| packages/api/src/microsoft_teams/api/auth/cloud_environment.py | Removes allowed_service_urls field and preset values from CloudEnvironment. |
heyitsaamir
approved these changes
Apr 28, 2026
singhk97
approved these changes
Apr 28, 2026
Addresses review feedback. The cloud parameter on the constructor was added by the allowlist work and became dead after the revert. Sovereign cloud routing happens entirely inside the factory methods (for_service, for_entra), which derive valid_issuers, jwks_uri, and login_endpoint from cloud and bake them into JwtValidationOptions before construction. Restores the pre-allowlist constructor signature. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
Reverting the serviceUrl allowlist defense-in-depth feature before public release. Open design questions on the work item (default sovereign cloud domains, narrowing of
*.botframework.com, applying to proactiveConversationReferences, consultation with APX) should be resolved before this becomes part of the public API surface.This feature has not shipped in any release. Removing the public
additional_allowed_domainsoption is a breaking change for anyone building frommain, which is not ideal but acceptable since no release has been cut. Reverting now buys time to discuss without breaking customers later.Removed
is_allowed_service_urlhelperadditional_allowed_domainsoption onAppOptions/InternalAppOptions, plus plumbing throughApp->HttpServer->TokenValidator(for_service,for_entra,validate_token)CloudEnvironment.allowed_service_urlsfield and per-cloud entries (PUBLIC/US_GOV/US_GOV_DOD/CHINA)HttpServer.handle_requesttest_token_validator.pyandtest_http_server.pyPreserved (other security work bundled into PR #370)
tenant_idis missing infor_entraPreserved (sovereign cloud, separate work)
CloudEnvironmentpresets,with_overrides,from_name,cloudoption onApp, and thecloudparameter onTokenValidatorfactories are unchanged.Test plan
uv run ruff checkclean (full repo)uv run pyrightclean (full repo, 0 errors / 0 warnings)uv run pytest packages/apps/tests/: 246 tests passexamples/echostarts and uvicorn binds to port