Skip to content

Use golang-jwt/jwt instead of form3tech-oss/jwt-go #104007

@dims

Description

@dims

We used to have dgrijalva/jwt-go a while ago which was unmaintained. So folks switched to a fork in form3tech-oss org. However there is a community maintained fork at https://github.com/golang-jwt/jwt we should be using.

Links:

vendor/github.com/heketi/heketi/client/api/go-client/client.go:	jwt "github.com/form3tech-oss/jwt-go"
vendor/github.com/Azure/go-autorest/autorest/adal/token.go:	"github.com/form3tech-oss/jwt-go"
vendor/go.etcd.io/etcd/server/v3/auth/jwt.go:	jwt "github.com/form3tech-oss/jwt-go"
vendor/go.etcd.io/etcd/server/v3/auth/options.go:	jwt "github.com/form3tech-oss/jwt-go"

So what do we need to do? Persuade the folks maintaining the following repos to switch to the community fork.

By first filing issues to raise their awareness and following it up with PRs

/area code-organization

Metadata

Metadata

Labels

area/code-organizationIssues or PRs related to kubernetes code organizationkind/bugCategorizes issue or PR as related to a bug.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.sig/authCategorizes an issue or PR as relevant to SIG Auth.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

Status

Closed / Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions