We receive many requests at ActiveCampaign, and one very common request is to change our authentication scheme to incorporate a different system, whether that be ldap, another database -- you name it. It happens often enough that we have, for some time, left unencoded our authentication code so that people can modify it themselves if they wish. Not each product is the same in how they use authentication, but we'll try to explain as much as possible about how it works so that you can modify the scheme to your wishes.
Authenticator
Our older authentication, currently being phased out, is still in use in some of our products: namely, SupportTrio, iSalient and KnowledgeBuilder. In SupportTrio and iSalient, you'll find the Authenticator class in /ac_global/authlib; in KnowledgeBuilder, it's in /includes/extlib/authlib. The main function to modify is called authenticate.
AC Global Auth
Our newer authentication scheme is found in a file called /ac_global/functions/auth.php; it's used with 1-2-All, TrioLive, SwiftTraction. The equivalent of the authenticate function, in the above example, is here called ac_auth_login_md5. If you need the plaintext password, which is hashed before the call to that function, you can get it in ac_auth_login_plain.
Public Users in SupportTrio
Our authentication code for public users in SupportTrio, which is based on a different system than what we describe above, is also open. You can modify the code for that in the function_user.php file, located in the public functions directory.
