Bug 1839621 - Openshift console needs to proxy users token for OpenShift Terminal
Summary: Openshift console needs to proxy users token for OpenShift Terminal
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.5.0
Assignee: cvogt
QA Contact: Gajanan More
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-25 04:39 UTC by Angel Misevski
Modified: 2020-07-13 17:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:41:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console-operator pull 432 0 None closed Bug 1839621: Grant Console SA permissions to read webhooks configurations 2020-06-21 07:15:42 UTC
Github openshift console pull 5332 0 None closed Bug 1839621: Add an ability to proxy requests to Che Workspace 2020-06-21 07:15:42 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:41:39 UTC

Description Angel Misevski 2020-05-25 04:39:20 UTC 
Description of problem:
In order to automatically log users in to a OpenShift Terminal, it is necessary for the user's token to be securely passed to a defined workspace pod.

Version-Release number of selected component (if applicable):
4.5

How reproducible:
Always

Steps to Reproduce:
1. Try to start workspace using terminal masthead button

Actual results:
User is not logged in once terminal opens

Expected results:
User's OpenShift user is logged in once terminal opens

Additional info:
Comment 5 errata-xmlrpc 2020-07-13 17:41:26 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2409
Note You need to log in before you can comment on or make changes to this bug.