Cognito Authorizer passthrough to Authentication Middleware
Maintainers usually reply within 1 day
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
- aws, csharp
- Domain
- api, authentication, backend, cloud
Research direction
No files or tests are named. Start by tracing the API Gateway Cognito UserPool authorizer context into the ASP.NET Authentication middleware, then compare local and deployed behavior. Done means the evaluated JWT is available to the middleware so existing [Authorize] attributes work without environment-specific checks.
Written by the indexing model from the issue text.
Description
Describe the feature
It would be great to have some functionality to provide the JWT token that is evaluated on API Gateway by the Cognito UserPool authorizer, to be 'passed' through to the ASP.NET Authentication middleware.
Use Case
Currently, I can't test locally. I need to deploy to AWS and debug the context object by using console output and grepping logs for the context object and the details contained within, that is provided to the Lambda function by API Gateway.
I think this would be helpful for portability and testing. This would allow the application to continue using the [Authorize] attributes and minimise conditional checks whether its being tested locally or in the cloud.
Proposed Solution
No response
Other Information
No response
Acknowledgements
- I may be able to implement this feature request
- This feature might incur a breaking change
AWS .NET SDK and/or Package version used
Latest published.
Targeted .NET Platform
.NET 8
Operating System and version
Ubuntu 24.04
- Dominant language
- C#
- Stars
- 1.7k
- Forks
- 503
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 14
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 aws/aws-lambda-dotnet
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
aws/aws-lambda-dotnet#2571 · 1 comment ·
Maintainers usually reply within 1 day
-
bug module/aspnetcore-support p2 queued
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
aws/aws-lambda-dotnet#1123 · 4 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 68/100
aws/aws-lambda-dotnet#2583 ·
Maintainers usually reply within 1 day
-
feature-request p2
Difficulty 4/5 3-5 days Newbie friendliness 68/100
aws/aws-lambda-dotnet#2572 · 1 comment ·
Maintainers usually reply within 1 day
-
feature-request p2
Difficulty 4/5 3-5 days Newbie friendliness 48/100
aws/aws-lambda-dotnet#2551 · 1 comment ·
Maintainers usually reply within 1 day
All issues in aws/aws-lambda-dotnet
Similar issues
-
area/navigationview 🧭 difficulty/starter 🚀 good first issue kind/bug platform/all project/navigation-lifecycle 🧬 triage/untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
unoplatform/uno#24925 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
DamianEdwards/ghcp-spend-tray#39 ·
Maintainers usually reply within 1 day
-
copilot documentation
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
[Rust][Flaky Test] multiple_deadlines_fire_in_order asserts a wall-clock gap instead of firing orderOpenCI/CD ⚒️ Flaky-tests 🐦
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
valkey-io/valkey-glide#7255 ·
Maintainers usually reply within 3 days
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 92/100
unoplatform/Uno.Core#99 ·