Mikołaj Nowak
Mikołaj Nowak
### Summary When kong returns `401 Unauthorized` response it should return `WWW-Authenticate` header with proper challenge. Key auth was missing this header on some responses. This PR also adds a...
### Summary When kong returns `401 Unauthorized` response it should return `WWW-Authenticate` header with proper challenge. HMAC auth was missing this header. ### Related PRs: - https://github.com/Kong/kong/pull/11792 - https://github.com/Kong/kong/pull/11794 -...
### Summary When kong returns `401 Unauthorized` response it should return `WWW-Authenticate` header with proper challenge. Ldap auth was missing this header on some responses. ### Related PRs: - https://github.com/Kong/kong/pull/11791...
### Summary When kong returns `401 Unauthorized` response it should return `WWW-Authenticate` header with proper challenge. Oauth2 was missing this header on some responses. ### Related PRs: - https://github.com/Kong/kong/pull/11791 -...
### Summary This commit adds action-conventional-commits gh action ### Checklist - [ ] ~N/A~ The Pull Request has tests - [ ] ~N/A~ A changelog file has been created under...
### Summary This is just a test PR that shows a few commit messages that fail validation. The PR that introduces actual mergeable change is here: https://github.com/Kong/kong/actions/runs/6814184927/job/18530469357?pr=11972 ### Checklist -...
### Summary ### Checklist - [ ] The Pull Request has tests - [ ] A changelog file has been created under `changelog/unreleased/kong` or `skip-changelog` label added on PR if...
### Summary When kong returns `401 Unauthorized` response it should return `WWW-Authenticate` header with proper challenge. JWT auth was missing this header. ### Related PRs: - https://github.com/Kong/kong/pull/11791 - https://github.com/Kong/kong/pull/11794 -...
### Summary Previously you could name an entity using a uuid however it wouldn't be retrievable from the API by it's name. Example: `GET /routes/` - where uuid was set...
### Description Audit Log request were previously sorted by `request_id`. With the upcoming changes they'll be sorted by `request_timestamp` descending - which is from latest to oldest. ### Testing instructions...