Bug 2096949

Summary:	Satellite API Documentation misses OAuth consumer secret
Product:	Red Hat Satellite	Reporter:	Vath Sok <vsok>
Component:	API	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	NEW ---	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.11.0	CC:	apatel
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vath Sok 2022-06-14 15:36:00 UTC

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.

Comment 1 Brad Buckingham 2023-07-21 21:06:39 UTC

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.