Created attachment 252207 [details] git diff for www/mod_auth_mellon ``` www/mod_auth_mellon: Update to 0.19.1 PR: ```
Thanks!
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=d7cbd7afdcb46c7148866ca4f548150b883b1fb4 commit d7cbd7afdcb46c7148866ca4f548150b883b1fb4 Author: Ryan Steinmetz <zi@FreeBSD.org> AuthorDate: 2024-07-21 15:09:27 +0000 Commit: Ryan Steinmetz <zi@FreeBSD.org> CommitDate: 2024-07-21 15:09:27 +0000 www/mod_auth_mellon: Update to 1.19.1 - Pet portlint PR: 280392 Submitted by: brnrd@ www/mod_auth_mellon/Makefile | 4 ++-- www/mod_auth_mellon/distinfo | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-)
that was quick!!! Noticed you have commits in the mod_auth_mellon repo. Any chance you have an idea how to add external cache capability for the tokens to this module? So one could create a cluster of apache servers sharing the tokens...
I don't believe that is functionality that exists within the module. If you search for "cache" in their PRs list, you'll find various people that have proposed adding support for it, but nothing that was clean/accepted. For redundant-host deployments, one can use consistent-hashing to ensure that a given user always gets balanced to the same backend node, provided that the node is online. You can also deploy hosts in an active/standby configuration to achieve similar results. That being said, I agree that lack of session-sharing ability is an issue.
Thanks Ryan! Was aware of those discussion threads, secretly hoping you had something I wasn't aware of. Apart from clustering, there's also the "All tokens are lost" on reload. Reloads are fast enough, but all clients need to re-auth. mod_auth_mellon seems to require quite a lot of compute for this, exhausting instances temporarily.