https://github.com/wolfman68/vMailpanel

https://www.itsmarttricks.com/force-users-to-change-their-linux-ldap-password/

https://ltb-project.org/documentation/self-service-password/1.0/install_debian

https://github.com/ltb-project/self-service-password

https://community.spiceworks.com/topic/1137403-openldap-how-to-let-users-change-passwords

https://www.google.com/search?client=ms-opera-mobile&channel=new&espv=1&sxsrf=ALeKk01aeBSJ_rF-MtmowHec_0zdGAQ7EQ%3A1586640481579&ei=YTaSXrf1Is_DgQacga7ACg&q=web-chpass+ubuntu&oq=web-chpass+ubuntu&gs_lcp=ChNtb2JpbGUtZ3dzLXdpei1zZXJwEAM6BAgjECc6BggAEAcQHjoECAAQHjoGCAAQBRAeOgUIIRCgAToHCCEQChCgAVChG1icb2CYdWgCcAB4AIABxgGIAdEMkgEEMC4xMJgBAKABAQ&sclient=mobile-gws-wiz-serp

https://github.com/courtney-rosenthal/web-chpass

In the LDAP configuration you can change the internal username in the expert tab. You might need to clear the mappings.

There are several things you must know before changing this:

• Changing the attribute isn’t supported once the system starts rolling. DO NOT change it in production.
• You might need to clear the stored mappings. Again DO NOT clear them in production since all the data associated to those users will be lost
• It’s your responsability to keep the attribute unique in the whole system. The object uuid is usually used for that. Expect issues if this isn’t respected.

I don’t know what options the 2FA system has, but I’d recommend to check them and try to solve it from there. We’re recommending to use the default uid (objectuid) because it’s guaranteed to be unique and give less issues.

Source: LDAP-User created with uid – Server – ownCloud Central

A pluggable authentication module (PAM) is a mechanism to integrate multiple low-level authentication schemes into a high-level application programming interface (API). It allows programs that rely on authentication to be written independent of the underlying authentication scheme. PAM was first proposed by Sun Microsystems in an Open Software Foundation Request for Comments (RFC) 86.0 dated October 1995. It was adopted as the authentication framework of the Common Desktop Environment. As a stand-alone open-source infrastructure, PAM first appeared in Red Hat Linux 3.0.4 in August 1996 in the Linux PAM project. PAM is currently supported in the AIX operating system, DragonFly BSD,^[1] FreeBSD, HP-UX, Linux, macOS, NetBSD and Solaris.

Since no central standard of PAM behavior exists, there was a later attempt to standardize PAM as part of the X/Open UNIX standardization process, resulting in the X/Open Single Sign-on (XSSO) standard. This standard was not ratified, but the standard draft has served as a reference point for later PAM implementations (for example, OpenPAM).

Source: Pluggable authentication module – Wikipedia

The Name Service Switch (NSS) is a facility in Unix-like operating systems that provides a variety of sources for common configuration databases and name resolution mechanisms. These sources include local operating system files (such as /etc/passwd, /etc/group, and /etc/hosts), the Domain Name System (DNS), the Network Information Service (NIS), and LDAP.

nsswitch.conf

A system administrator usually configures the operating system’s name services using the file /etc/nsswitch.conf. This lists databases (such as passwd, shadow and group) and one or more sources for obtaining that information. Examples for sources are files for local files, ldap for the Lightweight Directory Access Protocol, nis for the Network Information Service, nisplus for NIS+, and wins for Windows Internet Name Service.

Source: Name Service Switch – Wikipedia