Bug 2263953

Summary: remote_execution_effective_user_password no longer work when switching from one user to another
Product: Red Hat Satellite Reporter: matt jia <mjia>
Component: Remote ExecutionAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.14.1CC: akapse, aruzicka, jpasqual, rlavi, wclark
Target Milestone: UnspecifiedKeywords: MigratedToJIRA, PrioBumpGSS, Regression, Triaged
Target Release: Unused   
Hardware: All   
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:02:45 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 matt jia 2024-02-12 23:22:33 UTC
Description of problem:

As $subject and this stops working from 6.12 upwards.


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


How reproducible:

Easy

Steps to Reproduce:

1. Create a regular user (rexuser) on a system
2. On the same system create another user that will be the effective_user 
3. Allow ssh key to login with first user
4. Define a password for the effective_user
5. On Satellite, define the effective user method to su
6. Define the remote_execution_effective_user_password on satellite
7. try running a simple job

Actual results:
On Satellite:

su: Authentication failure

On the host /var/log/secure:

unix_chkpwd[20384]: password check failed for user (test)
su: pam_unix(su-l:auth): authentication failure; logname= uid=1000 euid=0 tty= ruser=rexuser rhost=  user=test

Expected results:

remote_execution_effective_user_password should take effect
 
Additional info:

Comment 2 Adam Ruzicka 2024-02-15 16:06:56 UTC
Also, from what I've seen this is specific to using su. Changing effective user with sudo and password should work

Comment 5 Eric Helms 2024-06-06 17:02:45 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.