[Spacewalk-list] PAM winbind support

[Paul Robert Marino]

Or it could be selinux you may want to check your audit log.
And just incase you are not familiar with selinux the audit2allow tool
along with the fixfiles tool are really simple
On May 1, 2012 5:42 PM, "Parsons, Aron" <parsonsa at bit-sys.com> wrote:

> It should still work fine; the 1.7 upgrade didn't break the two servers I
> have using winbind.  Remember that the process doing the PAM conversation
> is non-root unlike most other PAM-enabled services, so it may just be a
> simple permissions issue.  The likely culprit is the system keytab if you
> have Kerberos enabled.
>
> /aron
>
> -----Original Message-----
> Message: 1
> Date: Tue, 1 May 2012 13:46:31 -0400
> From: "Brown, Rodrick" <rbrown at knight.com>
> To: "spacewalk-list at redhat.com" <spacewalk-list at redhat.com>
> Subject: [Spacewalk-list] PAM winbind support
> Message-ID:
>        <
> C9C3C7FC93B40A4DA409F4B1ACB610991DBDFDEE7C at EXCHANGE10.global.knight.com>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Does spacewalk 1.7 still support PAM w/winbind ?
>
> After doing an upgrade to 1.7 I'm getting the following error in my tomcat
> logs
>
> 2012-05-01 13:39:07,267 [TP-Processor2] WARN
>  com.redhat.rhn.domain.user.legacy.UserImpl - PAM login for user User XXXXX
> (id 25, org_id 1) failed with error Authentication failure.
>
> I'm no longer able to login via spacewalk web with my PAM winbind setup.
> If I disable PAM authentication works fine.
>
> --RB
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20120501/82867b02/attachment.htm>