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

[Bug] Kyverno docs state that no authentication is used in external service calls but a bearer token is passed in the HTTP header #1308

Open
Dyex719 opened this issue Jul 17, 2024 · 1 comment
Assignees
Labels
bug Something isn't working
Milestone

Comments

@Dyex719
Copy link

Dyex719 commented Jul 17, 2024

Page link

https://kyverno.io/docs/writing-policies/external-data-sources/#variables-from-service-calls

Description

The kyverno docs under external service call state that:

At this time, authentication as part of these service calls is not supported.

However, a token is added to allow verification of the caller identity, using the token review API as seen here:
https://github.com/kyverno/kyverno/blob/main/pkg/engine/apicall/executor.go#L121

Expected behavior

Something along the lines of:

Authentication is provided by adding a bearer token to allow verification of the caller identity, using the token review API. At the moment, this token review API uses the default service account token as the bearer token.

Slack discussion

https://kubernetes.slack.com/archives/CLGR9BJU9/p1721163419677659

@Dyex719 Dyex719 added the bug Something isn't working label Jul 17, 2024
Copy link

welcome bot commented Jul 17, 2024

Thanks for opening your first issue here! Be sure to follow the issue template!

@JimBugwadia JimBugwadia self-assigned this Jul 17, 2024
@JimBugwadia JimBugwadia added this to the 1.13.0 milestone Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants