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

square/go-jose: error in cryptographic primitive #2970

Closed
yellowred opened this issue Apr 18, 2018 · 7 comments

Comments

@yellowred
Copy link

commented Apr 18, 2018

Steps to reproduce
$ kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml

secret "kubernetes-dashboard-certs" created
serviceaccount "kubernetes-dashboard" created
role "kubernetes-dashboard-minimal" created
rolebinding "kubernetes-dashboard-minimal" created
deployment "kubernetes-dashboard" created
service "kubernetes-dashboard" created

$ kubectl proxy
Starting to serve on 127.0.0.1:8001
Environment
Installation method: see above
Kubernetes version: v1.9.6
Dashboard version: v1.8.3
Commit: ec1d7de4456e6a397c7f931f0a2bfc74a6ca2e9c
Observed result

Dashboard reported Internal Server Error (500):

square/go-jose: error in cryptographic primitive

@yellowred

This comment has been minimized.

Copy link
Author

commented Apr 18, 2018

After I had deleted all the pods it started to work. So it was either resource caused or just needed more time to initialise. Gonna keep this issue for informational reasons, but closed as it is solved for me.

@yellowred yellowred closed this Apr 18, 2018

@tanmaykm

This comment has been minimized.

Copy link

commented Aug 26, 2018

Faced it too. It was because of a stale browser cookie in my case.

@rajatrai

This comment has been minimized.

Copy link

commented Dec 13, 2018

Faced it too, a bit annoying. In my case, I was using chrome and started a new window in incognito mode and it worked fine.

@xiaoanyunfei

This comment has been minimized.

Copy link

commented Dec 18, 2018

It maybe because your secret token was not encrypted and decrypted by the same pair private key and public key. kube-controller-manager generates the token, and kube-apiserver detects the token. the private key is specified by --service-account-key-file If unspecified, --tls-private-key-file is used.

@rajatrai

This comment has been minimized.

Copy link

commented Dec 18, 2018

It maybe because your secret token was not encrypted and decrypted by the same pair private key and public key. kube-controller-manager generates the token, and kube-apiserver detects the token. the private key is specified by --service-account-key-file If unspecified, --tls-private-key-file is used.

It didn't get that far where it takes the token ;-)

@njfix6

This comment has been minimized.

Copy link

commented Apr 19, 2019

Yes also get this issue. It happened to me when I switched between kubernetes clusters and I think it doesn't handle the token properly. If I log out and log back in it works.

@LevonBecker

This comment has been minimized.

Copy link

commented Jun 28, 2019

Had the same issue in Chrome. Clear Browser data fixes it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants
You can’t perform that action at this time.