Description of problem: In most of version, Satellite API documentation does not provide accurate information on how to use OAuth. One example: The doc said "Satellite does not sign the header..." but in fact it does require both consumer key and secret to sign header/request. How reproducible: Steps to Reproduce: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html-single/api_guide/index#Authenticating_API_Calls-OAuth_Authentication_Overview -> OAuth, most OAuth client required both key and secret. Actual results: - missing consumer secret Expected results: - A working example of OAuth client with both consumer key and secrete. Additional info: - If possible please provide a working code sample.
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.