Bug 1034560

Description of problem:
When working on SASL authentication in pmcd, it was noticed that use of the saslauthd mechanism did not complete the authentication correctly.  It appears to reject everything pmcd passes to it, including what pmcd believes to be valid username and password combinations.

We know these are making their way successfully into saslauthd, as it logs a message to its logfile saying authentication attempt rejected, every time.

Other forms of SASL authentication attempted appear to work as expected.

Once working, we should consider further whether this can be enabled by default.  The only other confounding factor here (AFAIK) is that to do so, we will need a packaging dependency on the saslauthd package - which may not be a default install.  It runs as root too (saslauthd, that is, as it needs to read the shadow passwd file), so it may be some people have a problem with having such a dependency in pcp.


Version-Release number of selected component (if applicable):
pcp-3.8.x and later.

How reproducible:
Every time.

Steps to Reproduce:
1. Configure /etc/sasl2/pmcd.conf to use saslauthd for password checking
2. Check detailed notes in lab.secure.html in pcp-doc package.
3. Attempt an authenticated connection

Actual results:
User is not authenticated, connection attempt is rejected.

Expected results:
User should be allowed to proceed on with an authenticated connection if valid credentials are passed, accessing performance data and so on.

Additional info: