Product Ideas Portal

Got an idea for a new feature? Maybe a tweak to make something work even better? Wish there was an integration with another product to make you even more productive? You've come to the right place.

The Product Ideas Portal lets you submit whatever product feedback you have, good, bad, ugly, and anywhere between.

Want to stay anonymous? No problem, you can still share your ideas with us. You can also create an account which lets you vote on other people's ideas and receive updates when your idea's status changes.

To learn more about how an idea becomes a feature, check out this infographic.


Allow integration with "pam_faillock.so" module such that both local system account and AD accounts do NOT get locked out of AD, but rather only locked out locally via pam_faillock.so module

Allow integration with "pam_faillock.so" module such that both local system accounts and AD based accounts do NOT get locked out of AD, but rather only locked out of the local system via pam_faillock.so module.

This functions with pam_tally2, but with RHEL8 pam_tally2 is deprecated per RedHat support. Therefore, we must leverage pam_faillock to lock out our service account and local accounts that do NOT use ADB.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Apr 20 2020
  • Unlikely to implement
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    20 Apr 05:46pm

    The following /etc/pam.d/password-auth and /etc/pam.d/system-auth files are configured on a test system in our environment and appear to provide the functionality we desire. The installation / joining of AD via ADB does not properly configure the files like this - we had to troubleshoot to find this config.