OIDC support

[Leo6Leo]

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).

• The announcement can be found here
• The corresponding GitHub issue can be found here
• The public design proposal can be found here
• 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.

Proposal

No response

Open questions

No response

[squakez]

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.

[github-actions]

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

[Leo6Leo]

/remove-stale