Description of problem:
In 4.8, we're removing the ability to create non-hashed tokens via the API. The OpenShift authenticator validating these tokens should reflect the change and refuse to validate token reviews that include these tokens.
Version-Release number of selected component (if applicable):
this is so that we don't forget about this aspect of the authenticator
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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.