serverless / serverless/serverless

Lambda Authorizer multiple identity sources with OR between them

Open
#11,233 16 comments 24 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs feedback
Dominant language
JavaScript
Stars
46.9k
Forks
5.7k
Avg merge
10h 7m
Merged PRs (30d)
57

Description

Is there an existing issue for this?
  • I have searched existing issues, it hasn't been reported yet
Use case description

Today there is already a feature where multiple identity source can be applied to lambda authorizer. The feature request can be seen here
As far as I understand, for this case, all the identity sources should be applied, otherwise API gateway will return 401 result automatically.
I would like to have the option that if ONE of the identity sources exists, then the lambda authorizer will be ran.
So for example if I have two identity sources:

  1. Authorization Header
  2. Cookie Header
  • If Cookie header exists and authorization header not exists - lambda authorizer will be ran
  • If Authorization header exists but cookie header not exists - lambda authorizer will be ran
  • If both Authorization and Cookie header not exists - API Gateway will return 401 automatically.

Is it a use case that can be implemented ?

Regards,
Nadav Mary

Proposed solution (optional)

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing multiple-identity-source Lambda authorizer behavior and the related feature request in issue #5746. Check AWS API Gateway semantics for missing identity sources, then define how the OR behavior should be represented and verified for the Authorization and Cookie header examples.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
api, authorization, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.