[FEATURE REQ] Managed Identity support for Backends
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure, csharp
- Domain
- authentication, backend-api-design, cloud
Research direction
Start by tracing how backend artifacts are extracted and how backendInformation.json serializes credentials; no source files or tests are identified in the issue. Compare the Azure managed identity fields shown in the portal with the artifact schema, then agree with maintainers on resourceId versus scope and verify the chosen configuration is included in extracted artifacts.
Written by the indexing model from the issue text.
Description
Please describe the feature.
In the Azure Portal I configured my backend credentials using a Managed Identity like this:
When I extract the artifacts, the managed identity configuration is not included in the backendInformation.json file:
{
"properties": {
"credentials": {
"header": {},
"query": {}
},
"protocol": "http",
"tls": {
"validateCertificateChain": true,
"validateCertificateName": true
},
"url": "https://test.com"
}
}
Would credentials be the place to store the managed identity properties?
For example:
{
"properties": {
"credentials": {
"managedIdentity": {
"clientId":"my-managed-identity-client-id",
"resourceId":"api://example-scope", // I used the name from the portal as a property name, which makes sense for Azure resource backends (e.g. Service Bus, Key Vault, etc), but from an app reg OAuth perspective the name "scope" would be better suited in my opinion
},
},
"protocol": "http",
"tls": {
"validateCertificateChain": true,
"validateCertificateName": true
},
"url": "https://test.com"
}
}
I am open to contributing it myself if the maintainers find it a good idea and we can agree on the implementation details before I start developing.
- Dominant language
- C#
- Stars
- 448
- Forks
- 247
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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.
More from Azure/apiops
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
priority-0
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
StackExchange/StackExchange.Redis#3249 ·
-
[Feat] 조합 영역 구분선 개선 Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100