Aquileo | Recent changes to feature-requests

Aquileo | #31 ZIMBRA_MALDUA_2FA config option

2025-12-16T12:04:07.595000Z

status: open --> closed

Aquileo | #31 ZIMBRA_MALDUA_2FA config option

2025-12-16T12:03:53.272000Z

Closing ticket.

Aquileo | #31 ZIMBRA_MALDUA_2FA config option

2025-11-21T19:27:36.318000Z

Documentation was updated to reflect that link.

You can close this feature request.

Thank you for this integration!

Aquileo | #31 ZIMBRA_MALDUA_2FA config option

2025-11-21T19:00:07.191000Z

It is checked in to this folder
https://sourceforge.net/p/zimbrabackend/code/HEAD/tree/zimbra-backend/misc/

Aquileo | #31 ZIMBRA_MALDUA_2FA config option

2025-11-21T18:50:48.583000Z

I didn't want to have that document tied to a Release as I envisaged having to update it independently whenever you made changes to the Maldua projects. Maybe I can create a separate folder in the code repository for the non Release specific stuff.

Aquileo | #31 ZIMBRA_MALDUA_2FA config option

2025-11-21T17:24:41.755000Z

So I would like to link to 'Adding-2FA-to-a-working-Zimbra-Z-Push-environment.txt' file from https://sourceforge.net/p/zimbrabackend/code/HEAD/tree/zimbra-backend/branches/z-push-2/ but it's not there. The file is not in https://sourceforge.net/p/zimbrabackend/code/HEAD/tree/zimbra-backend/release/75.1/ either.

It's only found in the download links. Can you upload it there so that I can link to non-downloaded version of it from my documentation?

Thank you!

Aquileo | #31 ZIMBRA_MALDUA_2FA config option

2025-11-18T13:21:52.390000Z

Good catch, Adrian.

It would likely only affect completely new installations as the installer script does not modify the config.php file - it asks the installer to manually compare the settings.

I have updated the code in the repo and in the tgz file.

Aquileo | #31 ZIMBRA_MALDUA_2FA config option

2025-11-18T12:35:33.472000Z

Release 75 has been just published - https://sourceforge.net/projects/zimbrabackend/files/Release75/ and it has the Maldua's 2FA support building.

However you should revert this release or either release 75.1 or 76.

//    define('ZIMBRA_CUSTOM_AUTH_PAGE','ZetaActiveSyncAuthRequest');

has ended up in the final config.php as commented out.

define('ZIMBRA_CUSTOM_AUTH_PAGE','ZetaActiveSyncAuthRequest');

which will make the installation to fail to anyone that does not have Maldua's ActiveSync Auth installed.

Aquileo | #31 ZIMBRA_MALDUA_2FA config option

2025-09-26T09:49:20.640000Z

This will be added for Release 75

Aquileo | ZIMBRA_MALDUA_2FA config option

2025-09-20T10:32:35.940000Z

So I have created: https://github.com/maldua-suite/zimbra-maldua-activesync .

Basically it enables you to use Application Passcodes as ActiveSync passwords while using Z-Push Bakend for Zimbra.

As the documentation says the way of using it it's just changing 'AuthRequest' to : 'ZetaActiveSyncAuthRequest' .

https://github.com/maldua-suite/zimbra-maldua-activesync?tab=readme-ov-file#initial-setup-z-push-vps-step-2-of-3

My Feature request ( I can implement it myself if needed) would be to add a configuration switch for using that new AuthRequest page so that it can be used in config.php directly.

Something like:

// Needs https://github.com/maldua-suite/zimbra-maldua-activesync extension installed on Zimbra
// ZIMBRA_MALDUA_2FA enables Application Passcodes to work seamlessly.
define('ZIMBRA_MALDUA_2FA', true);

I'm not proposing a patch directly because I'm not sure what would be the best name for the switch option.

How to add 2FA to Zimbra FOSS: https://github.com/maldua-suite/zimbra-maldua-2fa