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

[data-plane]: Kafka channel receiver: reject requests for wrong audience #3577

Closed
creydr opened this issue Jan 9, 2024 · 0 comments · Fixed by #3675
Closed

[data-plane]: Kafka channel receiver: reject requests for wrong audience #3577

creydr opened this issue Jan 9, 2024 · 0 comments · Fixed by #3675
Assignees

Comments

@creydr
Copy link
Contributor

creydr commented Jan 9, 2024

As the Eventing OIDC feature track describes, each Addressable gets its own Audience. In #3576 the Audience of a KafkaChannel will be exposed in its status, so sources can create OIDC tokens dedicated for this Audience.

When receiving an event, the kafka-channel-receiver must:

  • when the requested channel has no audience set:
    • no change in behavior
  • when the requested channel has an audience set:
    • when no / no valid Authorization header is provided
    • when a valid Authorization header is provided
      • check, if the provided OIDC tokens Audience aligns with the KafkaChannels audience
        • If if does not align: decline the request with a 401
        • If it aligns: no change in behavior

Additional Information:

@creydr creydr moved this to 📝 Draft in Eventing Sender Identity Jan 9, 2024
@creydr creydr self-assigned this Jan 25, 2024
@creydr creydr moved this from 📝 Draft to 📋 Backlog in Eventing Sender Identity Feb 2, 2024
@creydr creydr moved this from 📋 Backlog to 🔖 Ready in Eventing Sender Identity Feb 6, 2024
@creydr creydr moved this from 🔖 Ready to 👀 In review in Eventing Sender Identity Feb 6, 2024
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in Eventing Sender Identity Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant