Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add support for optional JWT authentication #3157

Merged
merged 5 commits into from
Apr 19, 2024

Conversation

ardikabs
Copy link
Contributor

@ardikabs ardikabs commented Apr 9, 2024

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #3081

@ardikabs ardikabs requested a review from a team as a code owner April 9, 2024 16:25
api/v1alpha1/jwt_types.go Outdated Show resolved Hide resolved
internal/ir/xds.go Outdated Show resolved Hide resolved
api/v1alpha1/jwt_types.go Outdated Show resolved Hide resolved
@ardikabs ardikabs force-pushed the feat/optional-jwt-auth branch 3 times, most recently from caedc38 to 122129d Compare April 12, 2024 15:43
@ardikabs
Copy link
Contributor Author

/retest

@@ -8,6 +8,10 @@ package v1alpha1
// JWT defines the configuration for JSON Web Token (JWT) authentication.
type JWT struct {

// AllowMissing determines whether a missing JWT is acceptable, defaulting to false if not specified.
// Note: Even if allowMissing is set to true, JWT authentication will still fail if an invalid JWT is presented.
AllowMissing *bool `json:"allowMissing,omitempty"`
Copy link
Contributor

@arkodg arkodg Apr 17, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hey @ardikabs, we discussed this in the community meeting last week, and most preferred Optional over AllowMissing , can we update this ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@arkodg
can we keep the naming convention AllowMissing in the IR while using Optional in the user interface (CRD)?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure sgtm

@ardikabs ardikabs force-pushed the feat/optional-jwt-auth branch from 122129d to b90ad69 Compare April 17, 2024 07:39
@ardikabs
Copy link
Contributor Author

/retest

@ardikabs ardikabs force-pushed the feat/optional-jwt-auth branch from b90ad69 to f744ddd Compare April 17, 2024 09:46
Copy link
Contributor

@arkodg arkodg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM thanks !

@arkodg arkodg requested review from zhaohuabing and a team April 19, 2024 03:02
@arkodg arkodg merged commit 4b69810 into envoyproxy:main Apr 19, 2024
20 checks passed
@ardikabs ardikabs deleted the feat/optional-jwt-auth branch April 19, 2024 04:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support optional JWT authentication for an endpoint
4 participants