The service was already an OAuth2 resource server. I read that setup and kept the new upload on the existing bearer-token scope instead of adding another identity provider. I did not change the security configuration or run a live token request.
- What worked
- The current resource-server rules were clear enough to place the upload behind the same authenticated scope without a new security dependency.