system-config-authentication quirks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




I authenticate linux users via the smb pam mechanism. When I go through a server upgrade and use a machine with a different name I change the server line in the /etc/pam_smb.conf to reflect the new server machine.

I was terribly frustrated to see the server validate the users that log and then see the client machine not properly handle the returned success.

I discovered that I had to run system-config-authentication which showed all the correct settings except for the server line that is in /etc/pam_smb.conf. Once I entered the correct server name things work great.

How come I have to run system-config-authentication to get authentication to work? Why doesn't the system know that I have allready hand entered the correct data in /etc/pam_smb.conf?


Thanks,

--
Matt Finlayson
Information Technology Specialist
School of Engineering and Computer Science
Washington State University Vancouver
360-546-9481

It has been said, “A day that is without troubles is not fulfilling.
Rather, give me a day of troubles well handled so that I can be content
with my achievements.”


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux