Description of problem:

Using SSSD in my PAM stack, I've found that when I set auth_provider = proxy and reference a new PAM configuration (proxy_pam_target = ncsu-proxy) that new PAM stack doesn;t work at all. 

I've confirmed this with sgallagh in #freeipa and his testing shows that the pam_proxy_target doesn't work for any library.  They all return "User not known to the underlying authentication module"

In my case I'm using the ncsu-proxy config which looks like this:

auth        required      pam_krb5.so 
password    required      pam_krb5.so use_authtok
session     optional      pam_krb5.so

With SSSD running this config I get errors:

May  7 15:26:47 kvmguest02 sssd_be: pam_krb5[2023]: error resolving user name 'jjneely' to uid/gid pair
May  7 15:26:47 kvmguest02 sssd_be: pam_krb5[2023]: error getting information about 'jjneely'
May  7 15:26:47 kvmguest02 sshd[2027]: pam_sss(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=foo.bar user=jjneely
May  7 15:26:47 kvmguest02 sshd[2027]: pam_sss(sshd:auth): received for user jjneely: 10 (User not known to the underlying authentication module)

Of course, getent passwd jjneely returns correct results (also provided by SSSD)

My workaround for the time being is to simply replace pam_sss in my PAM stack with pam_krb5.

Version-Release number of selected component (if applicable):
sssd-1.0.2-1.el6.i686