Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
There was a problem hiding this comment.
Pull request overview
This PR updates the production authentication scope returned by the runtime environment utilities for use when acquiring tokens to export observability telemetry.
Changes:
- Updated
PROD_OBSERVABILITY_SCOPEto a newapi://.../Agent365.Observability.OtelWritescope value.
|
|
||
| # Authentication scopes for different environments | ||
| PROD_OBSERVABILITY_SCOPE = "https://api.powerplatform.com/.default" | ||
| PROD_OBSERVABILITY_SCOPE = "api://9b975845-388f-4429-889e-eab1ef63949c/Agent365.Observability.OtelWrite" |
There was a problem hiding this comment.
The new PROD_OBSERVABILITY_SCOPE value is an explicit permission scope (…/Agent365.Observability.OtelWrite) rather than a resource /.default scope. If callers obtain tokens via client-credentials/managed identity flows, Azure AD typically requires requesting api://<app-id>/.default and will reject individual delegated scopes. Please confirm the intended auth flow for observability export and either switch this constant to the correct /.default scope or document/rename to make it clear this is a delegated scope that requires user context.
| PROD_OBSERVABILITY_SCOPE = "api://9b975845-388f-4429-889e-eab1ef63949c/Agent365.Observability.OtelWrite" | |
| PROD_OBSERVABILITY_SCOPE = "api://9b975845-388f-4429-889e-eab1ef63949c/.default" |
|
Thanks. Closing this PR as implemented below |
This pull request updates the authentication scope used for observability in the production environment. The change ensures that the correct resource identifier is used for authentication.
Authentication scope update:
PROD_OBSERVABILITY_SCOPEinenvironment_utils.pyto use a resource-specific identifier instead of a generic default scope.