microsoft / microsoft/azure-container-apps
Feature Request: Skip authentication for internal requests
Nobody has claimed this yet.
- Dominant language
- Bicep
- Stars
- 445
- Forks
- 54
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 3
Description
Is your feature request related to a problem? Please describe.
Having two container apps "app-a" and "app-b".
"app-a" is set up to be external with authentication enabled. "app-b" needs to call an api for "app-a" via "http://app-a/api". Currently this doesn't work as app-a will block unauthenticated requests. However authentication is not required for service to service communication in our case and it would be nice if it could be skipped.
Describe the solution you'd like.
Provide an option to skip authentication if the request comes from another app in the same container app environment.
external -> app-a = should require authentication
appb -> app-a = should not require authentication
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how authentication is enforced for requests to an Azure Container App and how requests between apps in the same container app environment are identified. Define the behavior for external-to-app-a and app-b-to-app-a requests, then confirm the approach preserves authentication for external callers while allowing the requested internal calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- authentication, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100