
#%PAM-1.0
auth required pam_env.so
auth sufficient pam_krb5.so no_user_check
auth required pam_deny.so
account required pam_krb5.so no_user_check
Please note that changing the password on the RHN website changes only the local password
on the RHN Satellite Server, which may not be used at all if PAM is enabled for that user. In the
above example, for instance, the Kerberos password will not be changed.
10. Enabling Push to Clients
In addition to allowing client systems to regularly poll the Satellite for scheduled actions, you
may enable the Satellite to immediately initiate those tasks on Provisioning-entitled systems.
This bypasses the typical delay between scheduling an action and the client system checking in
with RHN to retrieve it.
Important
SSL must be employed between the Satellite and its clients systems for this
feature to work. If the SSL certificates are not available, the daemon on the client
system fails to connect.
To take advantage of this feature, you must first configure your firewall rules to allow
connections on the required port(s), as described in Section 4, “Additional Requirements”.
Then you must install the osa-dispatcher package, which can be found in the RHN Satellite
Server software channel for the Satellite within the central RHN website. Once installed, start
the service on the Satellite as root using the command:
service osa-dispatcher start
Finally, install the osad package on all client systems to receive pushed actions. The package
can be found within the RHN Tools child channel for the systems on the RHN Satellite Server.
Once installed, start the service on the client systems as root using the command:
service osad start
Like other services, osa-dispatcher and osad accept stop, restart, and status commands,
as well.
Enabling Push to Clients
69
Comentarios a estos manuales