Knative has newly released an experimental feature: OIDC (OpenID Connect) support for event delivery in Knative Eventing. This feature aims to enhance security by enabling authenticated event delivery within the cluster. Adding this support to Camel-K will help align with Knative Eventing's new capabilities and the events can be published to a protected endpoint (sink).
Knative Sender Identity project board can be found here.
Problem
Currently, event delivery within the cluster is unauthenticated, and addressable event consumers (in camel-K's case, it is the knative sinks/kamlet sinks) cannot determine the identity of any sender. This poses a significant security challenge for businesses that require authenticated event delivery.
Thanks for the feature request. Just a little notice though. The Knative feature is still marked as "experimental". Any contribution is welcome as usual anyway.
Requirement
Knative has newly released an experimental feature: OIDC (OpenID Connect) support for event delivery in Knative Eventing. This feature aims to enhance security by enabling authenticated event delivery within the cluster. Adding this support to Camel-K will help align with Knative Eventing's new capabilities and the events can be published to a protected endpoint (sink).
Problem
Currently, event delivery within the cluster is unauthenticated, and addressable event consumers (in camel-K's case, it is the knative sinks/kamlet sinks) cannot determine the identity of any sender. This poses a significant security challenge for businesses that require authenticated event delivery.
Proposal
No response
Open questions
No response