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

Authentication failed because "/" endpoint returns 403 #21

Closed
cscetbon opened this issue Oct 17, 2018 · 11 comments
Closed

Authentication failed because "/" endpoint returns 403 #21

cscetbon opened this issue Oct 17, 2018 · 11 comments
Labels

Comments

@cscetbon
Copy link

I can query my k8s cluster using my certiticates and key :

k cluster-info
Kubernetes master is running at https://......
Grafana is running at http://......
Heapster is running at https://.....
KubeDNS is running at https://..../proxy
Kubemonitor is running at http://.....

But kubebox complains and asks me for a username/password/token.
screen_shot_2018-10-17_at_2_45_55_pm

Any workaround ?

@astefanutti
Copy link
Owner

May be related to #7.

@cscetbon
Copy link
Author

@astefanutti yeah probably

@astefanutti
Copy link
Owner

Let me close this as it is followed-up in #7.

@astefanutti
Copy link
Owner

Kubebox assumes user is granted permission to discover master API endpoints, though that is not always the case, e.g.:

$ kubectl get --raw /
Error from server (Forbidden): forbidden: User "cscetbon" cannot get path "/"

@astefanutti astefanutti reopened this Oct 24, 2018
@astefanutti astefanutti changed the title Cannot authenticate using server/client certificats/key Authentication failed because "/" endpoint returns 403 Oct 24, 2018
@astefanutti
Copy link
Owner

@cscetbon could you check what returns the following:

$ kubectl get --raw /apis

@cscetbon
Copy link
Author

@astefanutti
Copy link
Owner

astefanutti commented Oct 24, 2018

@cscetbon thanks. I just wanted to confirm you can access it.

It should be possible to make the call to / optional in Kubebox.

@cscetbon
Copy link
Author

Eager to test and see it in action 😉

@sabrehagen
Copy link

Me too. Do you have a fix in a branch we could test?

@astefanutti
Copy link
Owner

I plan to have this issue fixed for the upcoming release 0.3.2.

@astefanutti
Copy link
Owner

It should be fixed with 98b9c33. I'll cut a new release with the fix ASAP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants