-
JWT Authentication: Building a Hybrid Model That Actually Works
Part 2 of 4: Architectural Evolution in Horde 6 In part 1 of the evolution series: The jQuery Problem I discussed frontend concerns – How to move off a dead mobile-only framework towards a mobile-first responsive design and not get caught in the next framework I don’t need. This time we move towards authentication concerns.
-
The jQuery Mobile Problem: Why Horde 6 Had to Move On
Part 1 of 4: Architectural Evolution in Horde 6 Turns out you can’t ship a stable release while depending on a framework that was deprecated five years ago. I sort of knew this deep down in my head. Yes, yes, unmaintained dependencies are a problem. But the full weight of it didn’t hit me until
-
Horde’s new Two-Factor API
New Horde 6 feature: The horde/horde base app’s next release supports two factor logins.Dmitry Petrov is working to release a new One-Time Password module which integrates with this new API. Seemless integration for One Time Passwords. Several years ago I did some downstream development for a customer. They wanted to use One Time Passwords (OTP)
-
Sunsetting the Maintaina Horde Fork
A few years back I started a downstream fork of Horde to develop features I needed for foss and customer deployments without upstream dependencies. It went successful, was a great learning opportunity and a good exercise in critiquing our old tool chain and approaches. We had some well-known downstream users and contributors but I’d say
-
PHP: The case for standalone null parameters
PHP 8.0 introduced null and false as members of union types but disallowed them as standalone parameter types. PHP 8.2 changed that and allowed null as standalone parameter types. What is this good for? Should they extend this to “never” one day? Why do I call standalone null parameters poor man’s generics? What’s a null parameter?
-
A wicked problem from the past
In the last few evenings there was great despair. Trying to solve one problem would reveal yet another one. As a result, I hesitated to release some of the changes immediately. I don’t want to make people suffer, having to deal with new improved problems of the day whenever they run an update on their
-
Proxy Mode in horde-installer-plugin
null
-
Unit Testing Horde 6
Some years ago I reasoned about upgrading unit tests from ancient PHPUnit 4 to then-recent PHPUnit 9.Back then Horde’s unit test suite would use a Horde_Test class inheriting from the actual phpunit test cases. Even then I was fairly certain that this approach was not very practical in the long run.Why extending PHPUnit might be
-
I want to run horde/components on new PHP
If you want to run horde-components on a version of PHP which is not yet reflected in packagist.org released versions: me@mine:~/horde/components$ composer config minimum-stability devme@mine:~/horde/components$ composer install –ignore-platform-reqs No composer.lock file present. Updating dependencies to latest instead of installing from lock file. See https://getcomposer.org/install for more information.Loading composer repositories with package informationUpdating dependenciesLock file operations: