authmgr(4gx)

πŸ“¦
version 3.6 Β· 2 versions
, in alpine 3.24

πŸ’… NAME πŸ’…

ok so like β€” authmgr is the demultiplexer for authentication requests, and yes bestie, "demultiplexer" is a real word, we're gonna get through it together 🫢

This page lives in the Gromox admin reference, section 4gx. Hiiii, welcome, come in, sit down πŸ’–


✨ DESCRIPTION ✨

authmgr is the component that handles mail account authentication, and the whole vibe is that it dynamically selects the authentication backend per user account. Not one giant backend for everyone β€” per account. Lowkey iconic of it. πŸ‘‘


πŸŽ€ CONFIGURATION DIRECTIVES πŸŽ€

The usual config file location is /etc/gromox/authmgr.cfg β€” that's where it hangs out, that's its home. 🏠

  • auth_backend_selection β€” this baby controls how authmgr will verify passwords supplied with login operations. The details live down in the Authentication modes section, so go look there, iykyk πŸ‘€
    • Available: deny_all, allow_all, ldap, pam
    • Default: ldap

🌈 AUTHENTICATION MODES 🌈

okay, the actual modes, let's go mode by mode, no skips, no cap ⭐

  1. deny_all β€” literally every single attempt at authentication gets rejected. That's the whole thing. This is at best useful for testing (so, like, a vibe check for your config, not a lifestyle πŸ’€).
  2. allow_all β€” every attempt at authentication is permitted, provided the user exists. Handy when you're doing the initial mass-import of mailboxes via external IMAP-to-IMAP synchronization utilities such as imapsync, without needing to actually know the user passwords. πŸ™ˆ Big "just get the mailboxes in here" energy.
  3. ldap β€” old name: externid. authmgr will selectively pick LDAP/MySQL, depending on whether the externid column in the user database has a value or contains just the empty string. The particular value is ignored β€” it's only meaningful to the importer. πŸ¦‹
  4. pam β€” authmgr will selectively pick PAM/MySQL. The PAM service name will be "gromox".
🚨 IMPORTANT bestie, listen to me: be sure that pam_gromox.so is not invoked as part of that PAM service stack, or it will lead to infinite recursion. Like a mirror in a mirror in a mirror. Do not do this. 😭

🧚 SIGNALS 🧚

Upon receipt of SIGHUP, configuration files are re-read β€” BUT πŸ’… only a few select directives can actually be changed this way, because many parts just do not implement reload. So, like, temper your expectations. It's giving "I re-read the config but I'm not changing for you." πŸ’€


πŸ’œ SEE ALSO πŸ’œ

go read those too, bestie, I believe in you πŸ“


kisses and bye-bye πŸ’– this was the authmgr(4gx) page from the Gromox admin reference β€” the authmgr(4gx) manual, specifically, so you know exactly where you are. Mwah, go authenticate responsibly βœ¨πŸŽ€

πŸ“¦ where this page comes from