cancel
Showing results for 
Search instead for 
Did you mean: 
  • ×
    Information
    Know the Benefits of your HP account

    Connect with HP support faster, manage all your devices in one place, view warranty information and more– Click Here

    Information
    Fix Windows 10 Update Issues

    Resolve Windows 10 or update issues on HP computer or printer– Click Here

  • post a message
  • ×
    Information
    Know the Benefits of your HP account

    Connect with HP support faster, manage all your devices in one place, view warranty information and more– Click Here

    Information
    Fix Windows 10 Update Issues

    Resolve Windows 10 or update issues on HP computer or printer– Click Here

  • post a message
ArchivedThis topic has been archived. Information and links in this thread may no longer be available or relevant. If you have a question create a new topic by clicking here and select the appropriate board.
Highlighted
New member
2 1 0 0
Message 1 of 4
2,510
Flag Post

RGS is refusing connections and throwing errors

HP Recommended
RGS v7.33
Linux

I have built a Red Hat Enterprise WorkStation and installed RGS. We have a decent sized enterprise and have NIS handling logins for Linux and Windows Services handling logins for that platform.

 

We do offer single sign-ins for Linux users (you can use either set of credentials). I know this SSO scheme works because I can SSH to the test machine and log in using either set of credentials. If I try to login via RGS, the following is seen in rg.log.

 

05-18-17 07:57:06 INFO  - ReceiverDetails::isMatchFound - allowing connection via subnetmasking to IP address
05-18-17 07:57:18 ERROR - UnixSenderSecurityContext::authenticatePam::run - pam_authenticate failed.

 

Here are the relevent lines from /var/log/secure

 

May 18 07:57:18 hacl90 rgsender: PAM unable to dlopen(/lib64/security/pam_stack.so): /lib64/security/pam_stack.so: cannot open shared object file: No such file or directory
May 18 07:57:18 hacl90 rgsender: PAM adding faulty module: /lib64/security/pam_stack.so

 

I've been looking at this for two days and frankly, my eyes hurt. Any help would be greatly appreciated.

0 Kudos
3 REPLIES 3
Highlighted
Author
New member
2 1 0 0
Message 2 of 4
Flag Post
HP Recommended

Sorry guys. Almost forgot. The OS is RHEL 7.3

0 Kudos
Highlighted
Level 7
Level 7
375 370 29 35
Message 3 of 4
Flag Post
HP Recommended

What version of RHEL are you using?  If RHEL 7, this is a valid configuration.

Below is an example of an incorrect pam.d/rgsender

 

File: /etc/pam.d/rgsender

 

#%PAM-1.0

auth       required             /lib64/security/pam_nologin.so

auth       required             /lib64/security/pam_stack.so service=system-auth

 

-----------------------------------------------

 

It should look like this:

 

-------------------------------

File: /etc/pam.d/rgsender

#%PAM-1.0

auth  required  pam_env.so

auth  required  pam_nologin.so

auth  include  system-auth

account  include  password-auth

session  include  password-auth

 

You could also try changing "auth include system-auth to auth include password-auth

 

Let me know if this helps.

I work on the behalf of HP.

 

I work on behalf of HP
Highlighted
Level 7
Level 7
375 370 29 35
Message 4 of 4
Flag Post
HP Recommended

Please uninstall, reboot, and then reinstall using our script. If you can’t use the script for install, then installing the sender package followed by the config package should give a good /etc/pam.d/rgsender file. They need to pay attention to any error messages from rpm.

 

The files we look at to detect the distro is one of these (it could change in the future)

  • /etc/redhat-release
  • /etc/SuSE-release
  • /etc/CentOS-release
  • /etc/os-release

 

If we fail to find expected results from one of these files, I would expect the config package to fail to install.

I work on behalf of HP
0 Kudos
ArchivedThis topic has been archived. Information and links in this thread may no longer be available or relevant. If you have a question create a new topic by clicking here and select the appropriate board.
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation