Bug 1821757 - OBC Data is showing Base64 encoded value
Summary: OBC Data is showing Base64 encoded value
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Storage Plugin
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.5.0
Assignee: Bipul Adhikari
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On:
Blocks: 1822531
TreeView+ depends on / blocked
 
Reported: 2020-04-07 14:19 UTC by Bipul Adhikari
Modified: 2020-07-13 17:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1822531 (view as bug list)
Environment:
Last Closed: 2020-07-13 17:26:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 4943 0 None closed Bug 1821757: Decode noobaa secret details before passing to SecretValue in OBC page 2020-06-23 09:52:04 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:26:31 UTC

Description Bipul Adhikari 2020-04-07 14:19:03 UTC
Description of problem:
The OBC details page shows base64 encoded value.

Version-Release number of selected component (if applicable):
4.3 and above

How reproducible:
1/1

Steps to Reproduce:
1. Create OBC and go to the details page
2. Open the secret related to OBC on a different page.
3. The value shown in OBC data(secret and access key) is encoded value of what is seen in the secret page.

Actual results:
The two values are different.


Expected results:
The two values should be equal(In secret and OBC data page).

Additional info:

Comment 3 Elena Bondarenko 2020-04-09 08:08:53 UTC
I tested with 4.5.0-0.nightly-2020-04-09-040908, OBC details page shows the same un-encoded values as the secret details page.

Comment 4 errata-xmlrpc 2020-07-13 17:26:04 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.