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

[2.9.0] 1373 support authentication with service account tokens #1402

Conversation

LucasSaintarbor
Copy link
Contributor

@LucasSaintarbor LucasSaintarbor commented Jul 24, 2024

Fixes #1373

Reminders

  • See the README for more details on how to work with the Rancher docs.

  • Verify if changes pertain to other versions of Rancher. If they do, finalize the edits on one version of the page, then apply the edits to the other versions.

  • If the pull request is dependent on an upcoming release, remember to add a "MERGE ON RELEASE" label and set the proper milestone.

Description

From issue:

Ranchers auth proxy can now support authentication of requests that specify a Service Account token in the Authorization Bearer header.

More info/context:

JWT Authentication is also known as Service Account Token Authentication.

This feature, when enabled, lets a user set up a downstream cluster to support authentication, through Rancher, of tokens that are created for a service account that exists on a downstream cluster (those tokens are in the form of a JWT).

Prior to this feature, Rancher would reject such requests because Rancher would only support Rancher-issued tokens (which are NOT JTWs). Some users worked-around this limitation by issuing those requests directly to the downstream cluster, rather than relying on Rancher's auth/security. With this feature enabled, users no longer have to work-around Rancher.

A common use case for this is to enable integration of secret vault solutions (like Hashicorp Vault). You can see the original rancher/rancher issue for more details rancher/rancher#22417.

Comments / Questions

Copy link
Contributor

@martyav martyav left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left some comments alongside edit suggestions.

@martyav martyav added the MERGE ON RELEASE Don't merge until the moment the next release publishes label Jul 24, 2024
@martyav martyav added this to the v2.9-Next1 milestone Jul 24, 2024
@LucasSaintarbor
Copy link
Contributor Author

LucasSaintarbor commented Jul 30, 2024

@crobby @samjustus May you provide a review when you get the chance? Thanks!

Copy link
Contributor

@crobby crobby left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is good. Accurate and concise.

@LucasSaintarbor LucasSaintarbor merged commit c3a33fb into rancher:main Aug 1, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
/docs file changed MERGE ON RELEASE Don't merge until the moment the next release publishes /versioned-docs file changed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support authentication with service account tokens
4 participants