Closed tvdijen closed 3 years ago
Thank you for reporting this. Could you test if this error also occurs when using PHP7.2?
I just did, and it doesn't...
Since version 4.0.0 php 7.2 is the supported version. The other components are also only tested on php 7.2.
We'll keep this issue open
That's unfortunate, because it all used to work fine on the 3.x branch & PHP 7.4.. It would be a pitty if an upgrade of this module (all the others seem to be working just fine) would mean I have to downgrade PHP.
@tvdijen Could you see if https://github.com/OpenConext/Stepup-RA/pull/249 fixes your issue?
Well, it prints a message instead of throwing an exception so that's better... Still doesn't allow me to start the vetting procedure though.
From config: loa_required_for_login: 'urn:rsa:names:tc:SAML:2.0:ac:classes:FIDO' stepup_loa_loa3: 'urn:rsa:names:tc:SAML:2.0:ac:classes:FIDO'
I've verified that the AuthnContextClassRef is present in the AuthnResponse and matches the above. I'm logged in as SRAA.
I've spent some more time trying to debug this, but my lack of experience with Symfony makes it difficult..
I was able to exclude the LOA's serialize/unserialize methods as possible causes.. What I can tell is that the Loa-property is simply not set on the container, but I'm not sure how/when/where it's supposed to be set, so I'm kinda stuck..
I've also tried a composer update
to make sure it's not a bug that has already been fixed upstream.
Any follow-up after three months please? This is becoming a deal-breaker for me..
As soon as the RA enters the activation code, the following error occurs: