Bug 2215034 - Insight client on GCP fail to authenticate on insight hosted service for PAYGO Rhel Instance
Summary: Insight client on GCP fail to authenticate on insight hosted service for PAYG...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: insights-client
Version: 8.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: CSI Client Tools Bugs
QA Contact: Red Hat subscription-manager QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-14 14:16 UTC by Mohamed Tleilia
Modified: 2023-07-05 13:37 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-05 13:36:53 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-159867 0 None None None 2023-06-14 14:18:24 UTC

Comment 2 Wei Shi 2023-06-27 06:54:19 UTC 
Hi,
  I'm not from insights team, so my response maybe not accurate.

  RHEL PAYG on GCP is managed by RHUI without a RH credential, basic authentication is needed for this scenario according to the document[1].

1. https://access.redhat.com/documentation/en-us/red_hat_insights/2023/html-single/deploying_red_hat_insights_on_existing_rhel_systems_managed_by_red_hat_update_infrastructure/index
Comment 3 Rich Jerrido 2023-07-05 13:36:53 UTC 
This behavior isn't a bug. 

To connect a system, any system, to Red Hat, you need to authenticate. 

Running `insights-client --test-connection` on a system that is receiving its content from RHUI will have exactly the effect as described in the opening comment. 


Valid and supported methods for connecting systems to Red Hat are described here (https://access.redhat.com/documentation/en-us/subscription_central/2023/html-single/getting_started_with_rhel_system_registration/index#basic-reg-rhel-cli) 


The basic authentication method, as described in Comment #2 is deprecated and will be removed in the future.
Note You need to log in before you can comment on or make changes to this bug.