Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[TT-16013] Gateway panics when validating JWT claims #7530
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
Uh oh!
There was an error while loading. Please reload this page.
[TT-16013] Gateway panics when validating JWT claims #7530
Changes from all commits
c58fdc3fea175ecb2637597b8fc36bdefd71809dd60f18da20b4a04cf14f4e5c8b0efec042d35296dd3f65bd416File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Check failure on line 51 in apidef/oas/authentication.go
architecture Issue
Raw output
Check warning on line 105 in apidef/oas/authentication.go
architecture Issue
Raw output
Check failure on line 216 in apidef/oas/authentication.go
architecture Issue
Raw output
Check failure on line 216 in apidef/oas/authentication.go
logic Issue
Raw output
Implement the `decodeScheme` function. It should inspect the input `map[string]interface{}` to determine the type of security scheme (e.g., by checking keys like `type`, `scheme`, `bearerFormat`) and then use a library like `mapstructure` to decode the map into the corresponding struct pointer (e.g., `*JWT`, `*Token`).Check failure on line 229 in apidef/oas/authentication.go
logic Issue
Raw output
Implement the `decodeScheme` function. It should inspect the raw `interface{}` data to determine the concrete type of the security scheme (e.g., by checking for fields unique to JWT, Basic, Token, etc.) and then correctly unmarshal the data into the corresponding struct type.Check failure on line 230 in apidef/oas/authentication.go
logic Issue
Raw output
Implement the `decodeScheme` function to correctly identify the type of security scheme from the raw `interface{}` data (likely a `map[string]interface{}`) and decode it into the corresponding struct (e.g., `*Token`, `*JWT`, etc.). This will likely require inspecting fields to determine the scheme type, similar to the logic in the `importNative` function.Check notice on line 251 in apidef/oas/authentication.go
performance Issue
Raw output
Check notice on line 276 in apidef/oas/authentication.go
performance Issue
Raw output
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.