Hi,
Since upgrading from 6.6 to 7.0, we had some memory leak like behavior: +500M
used memory per week.
After investigation, it only occurs when you have many many different CAS
"service" urls (query params are taken into account)
For example https://userphoto.univ.fr/?uid=xxx&v=
The culprit
Thanks a lot for that ! I hope someone will fix it with your fix.
Until now, I had to register my webauthn devices for testing by accessing
directly to a service protected by webauthn
Regards,
Le jeudi 5 décembre 2024 à 15:19:01 UTC+1, P Assenger a écrit :
> Two PRs should correct the issue wit
Hi Pierre,
oh I mean by accessing directly to a service protected by mfa-gauth, just
after the login/pwd form : You have the ability to register a new device
here.
The other way is to register your device thru the /cas/login page (in case
you added this functionnality ...)
it does not work for e
Two PRs should correct the issue with webauthn device registration. I do
not know if the crossover with mfa-gauth is also corrected, as I wanted
to get webauthn registration working for POC purpose, only.
Note that, for now, the two PRs are rejected as there is no test associated
to them:
