Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1493679 - can't get token from https://api.free-int.openshift.com/oauth/token/request
can't get token from https://api.free-int.openshift.com/oauth/token/request
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Auth (Show other bugs)
3.7.0
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 3.7.0
Assigned To: Mo
Chuan Yu
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-09-20 13:13 EDT by Peter Ruan
Modified: 2017-11-28 17:12 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-11-28 17:12:03 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3188 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update 2017-11-28 21:34:54 EST

  None (edit)
Description Peter Ruan 2017-09-20 13:13:05 EDT
Description of problem:

trying to get a token from https://api.free-int.openshift.com/oauth/token/request but getting the error, 'Error getting token: The client is not authorized to request a token using this method.'  I was able to get a token a couple of days ago using the same url and I can still log into the web GUI. 

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


How reproducible:
always

Steps to Reproduce:
1. log into free-int via web https://console.free-int.openshift.com/console/
2. request a token from https://api.free-int.openshift.com/oauth/token/request   using your redhat account 
3.

Actual results:
Error getting token: The client is not authorized to request a token using this method. 


Expected results:
get a valid token.

Additional info:
Comment 1 Mo 2017-09-20 18:31:17 EDT
That cluster is running 3.7.0-0.125.0

The fix for this is in 3.7.0-0.126.0 and v3.7.0-0.126.1
Comment 4 Wang Haoran 2017-09-29 22:08:37 EDT
it works well now on the free int, move to verified.
Comment 8 errata-xmlrpc 2017-11-28 17:12:03 EST
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/RHSA-2017:3188

Note You need to log in before you can comment on or make changes to this bug.