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.

Sign up for GitHub

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

Jump to bottom

Add more mechanisms to provide OpenShift tokens to Kiali #5127

Closed
lucasponce opened this issue May 27, 2022 · 0 comments · Fixed by #5133
Closed

Add more mechanisms to provide OpenShift tokens to Kiali #5127

lucasponce opened this issue May 27, 2022 · 0 comments · Fixed by #5133
Assignees
@israel-hdez
Labels
backlog Triaged Issue added to backlog enhancement This is the preferred way to describe new end-to-end features.

Comments

@lucasponce
Copy link
Contributor

One of the authentication mechanisms supported by Kiali is OpenShift [1].

In the context of the integration of Kiali with other OpenShift platforms, it may happen that the user is already authenticated and a valid token is already stored in the browser.

Kiali could extend the mechanism that this token can be received (HTTP headers or web parameters) to support more rich integration scenarios.

[1] https://kiali.io/docs/configuration/authentication/openshift/
@lucasponce lucasponce changed the title Add more mechanism to provide OpenShift tokens to Kiali Add more mechanismd to provide OpenShift tokens to Kiali May 27, 2022
@lucasponce lucasponce changed the title Add more mechanismd to provide OpenShift tokens to Kiali Add more mechanisms to provide OpenShift tokens to Kiali May 30, 2022
@lucasponce lucasponce added backlog Triaged Issue added to backlog enhancement This is the preferred way to describe new end-to-end features. labels May 30, 2022
israel-hdez added a commit to israel-hdez/swscore that referenced this issue May 30, 2022
@israel-hdez
OpenShift auth: Allow sessions from 3rd parties
bd62f68 
The third party must modify every request and inject an OpenShift token via the HTTP `Authorization` Header (preferred) or via the URL `oauth_token` parameter.

Fixes kiali#5127.
@israel-hdez israel-hdez mentioned this issue May 30, 2022
Merged
lucasponce pushed a commit that referenced this issue Jun 1, 2022
@israel-hdez
OpenShift auth: Allow sessions from 3rd parties (#5133)
9a15fff 
* OpenShift auth: Allow sessions from 3rd parties

The third party must modify every request and inject an OpenShift token via the HTTP `Authorization` Header (preferred) or via the URL `oauth_token` parameter.

Fixes #5127.

* UI to inject the OpenShift token if received in the URL.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@israel-hdez israel-hdez

Labels
backlog Triaged Issue added to backlog enhancement This is the preferred way to describe new end-to-end features.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

OpenShift auth: Allow sessions from 3rd parties israel-hdez/swscore
2 participants
@lucasponce @israel-hdez