[Archived PR] feat(auth): implement Entra ID authentication in API
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- azure, typescript
- Domain
- api, authentication, backend, database
Research direction
The archived PR names user routes, the users collection migration, ClaimsProfileEnricher, EntraIdAuthProvider, authentication configuration, and the user schema; start by reviewing those entry points and the authentication configuration, claims enricher, and Entra ID provider tests. First verify whether this work exists elsewhere, since the payload identifies it as an archived PR; completion would include the listed modules, dependencies, routes, migration, schema, and passing tests.
Written by the indexing model from the issue text.
Description
Original author: @cmaneu
…ement
- Add user routes for fetching authenticated user identity.
- Create users collection migration with unique identity key and email index.
- Introduce ClaimsProfileEnricher for enriching user profiles from token claims.
- Implement EntraIdAuthProvider for verifying access tokens and extracting identity claims.
- Add configuration loading for authentication settings from environment variables.
- Create user schema for user documents in the database.
- Add tests for authentication configuration, claims enricher, and Entra ID provider.
- Update shared package to include new authentication modules and dependencies.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 5
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 26
Getting set up
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 microsoft/scope
-
type: worker-update
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
type: worker-update
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
type: worker-update
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
author: JaGord documentation good first issue UI
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
author: cedricvidal bug portal
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
Similar issues
-
enhancement providers-api ui-dashboard
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
external-issue to-triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
needs triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
homarr-labs/homarr#6976 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day