Skip to content

update docs for self-assigned JWTs#1116

Open
Ishan-gupta2005 wants to merge 1 commit intoetcd-io:mainfrom
Ishan-gupta2005:docs/jwt-token-auth-design
Open

update docs for self-assigned JWTs#1116
Ishan-gupta2005 wants to merge 1 commit intoetcd-io:mainfrom
Ishan-gupta2005:docs/jwt-token-auth-design

Conversation

@Ishan-gupta2005
Copy link

@Ishan-gupta2005 Ishan-gupta2005 commented Feb 4, 2026

Description

Updates etcd v3 authentication design under learning section to clarify how users can directly set JWT tokens at client initialization.

Changes

  • Documents JWT token direct setting capability for users managing tokens externally
  • Documents Use cases and workflow
  • Documents how it differs from standard authentication
  • Applied consistently across v3.5, v3.6, and v3.7 documentation

Related Issues

#1088 : Update docs for self-managed JWTs
etcd-io/etcd#19863: Allow users to set a JWT token directly

@k8s-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Ishan-gupta2005
Once this PR has been reviewed and has the lgtm label, please assign spzala for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot
Copy link

Hi @Ishan-gupta2005. Thanks for your PR.

I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@ronaldngounou
Copy link
Member

Thank you for your contribution @Ishan-gupta2005 . This is very a very useful information to be updated.

@ronaldngounou
Copy link
Member

ronaldngounou commented Feb 4, 2026

/retest

@ronaldngounou
Copy link
Member

@Ishan-gupta2005 Could you please address the lint failures?

@Ishan-gupta2005
Copy link
Author

Thanks for pointing that out! I’ll review the lint errors and push fixes as soon as possible

Relates to #19863: Allow users to set a JWT token directly

Signed-off-by: Ishan-gupta2005 <guptaishan337@gmail.com>
@Ishan-gupta2005 Ishan-gupta2005 force-pushed the docs/jwt-token-auth-design branch from b7394c0 to bd9df31 Compare February 4, 2026 10:46
@k8s-ci-robot k8s-ci-robot removed the lgtm label Feb 4, 2026
@k8s-ci-robot
Copy link

New changes are detected. LGTM label has been removed.

@Ishan-gupta2005
Copy link
Author

/retest

@k8s-ci-robot
Copy link

@Ishan-gupta2005: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@Ishan-gupta2005
Copy link
Author

@ronaldngounou I've fixed all the linting issues that were reported and verified locally by running the linting script. I hope it's ready for review now.

@ronaldngounou
Copy link
Member

/retest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants