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

User should be automatically authenticated on OpenShift in his workspaces #13449

Closed
slemeur opened this issue May 30, 2019 · 3 comments
Closed
Labels
kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@slemeur
Copy link
Contributor

slemeur commented May 30, 2019

Description

When Eclipse Che is deployed on OpenShift, he should automatically be authenticated from his workspaces to his OpenShift namespace.

Linked Issues

redhat-developer/rh-che#541
#13447

@slemeur slemeur added the kind/enhancement A feature request - must adhere to the feature request template. label May 30, 2019
@sleshchenko
Copy link
Member

Just wanted to mention that previously it was done using OSIO installer https://github.com/redhat-developer/rh-che/blob/master/plugins/fabric8-multi-tenant-manager/src/main/resources/installers/1.0.0/com.redhat.oc-login.script.sh
And in Che 7 installers mechanism is deprecated. It is needed to find another way to implement it.

We are able to mount service account token with namespace admin rights, but not on every installation user is able to create such. And even if he has - he will have a token only to current namespace but not all his workspaces.

AFAIK There is no way to grant workspace access to all user's namespace except injecting user token( but it's needed to find a proper way to do it), but it may expire (for OSIO it's not so critical since expiration time is very long, but in general for any OpenShift installation it may be an issue).

Also, wanted to clarify: in which containers of workspace it should be done? In everyone that has oc client?

@che-bot
Copy link
Contributor

che-bot commented Nov 27, 2019

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 27, 2019
@slemeur
Copy link
Contributor Author

slemeur commented Dec 2, 2019

Will be solved by #15261

@slemeur slemeur closed this as completed Dec 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants