Bug 2283134

Summary:	containter_gateway on capsules returns success for login attempts with no username/password informed
Product:	Red Hat Satellite	Reporter:	Joniel Pasqualetto <jpasqual>
Component:	Container Management - Content	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.15.0	CC:	iballou, rlavi
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, 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:	2024-06-06 17:40:13 UTC	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 Joniel Pasqualetto 2024-05-24 18:46:05 UTC

Description of problem:

Trying to login into a capsule registry (handled by smart-proxy containter_gateway), a user gets a "Login Succeeded!" when no username/password are informed.

Providing any bad username/password user gets the expected authentication error.

Success message is is misleading, since no actual authentication happened and no protected content can be pulled.

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

Observed on 6.14 and 6.15

How reproducible:

Always

Steps to Reproduce:

1. Try running "podman login mycapsule.example.com" and don't inform username or password:

~~~
# podman login mycapsule.example.com
Username: 
Password: 
Login Succeeded!
~~~


Actual results: 
  user gets a login succeeded message


Expected results: 
  authentication should fail if no username/password was informed


Additional info:

Comment 1 Eric Helms 2024-06-06 17:40:13 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.