Adding pam_ldap.so by masking pam load errors

Absence of ldap distro feature will not generate pam_ldap.so because
of which we might see some unwanted error messages regarding the
failure in opening the pam_ldap.so in journalctl incase if pam_ldap
is present in PAM Configuration.

This commit would:

- Leverage '-' option before the 'type' in pam configuration, by which
  the PAM library will not log any errors in the syslog if it is not
  able to load the module beacause it is missing in the system.By using
  this we don't need two pam configuration files for ldap and unix.
- Leverages ignore_unknown_user &  ignore_authinfo_unavail options of
  pam_ldap.so, which forces the PAM framework to ignore pam_ldap incase
  if the user is not present in LDAP server or if the client cannot
  connect to LDAP Server.

Change-Id: Ib876f942bf9318c37b3683bc5491a158c0f0e40e
Signed-off-by: manojkiraneda <manojkiran.eda@gmail.com>
2 files changed
tree: ac9efca046519268a950d80a2b20b26ed99bdd68
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. recipes-connectivity/
  6. recipes-core/
  7. recipes-devtools/
  8. recipes-extended/
  9. recipes-phosphor/
  10. recipes-protocols/
  11. recipes-support/
  12. recipes-textproc/
  13. COPYING.apache-2.0
  14. COPYING.MIT
  15. LICENSE
  16. MAINTAINERS
  17. README.md
  18. recipes.txt
README.md

OpenBMC

meta-phosphor is the OpenBMC layer. This layer should be included for all OpenBMC systems. The OpenBMC layer contains content which is shared between all OpenBMC systems.