This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

6.4.2.1 broke fido2 multiple categories

After upgrading server to 6.4.2.1, the multiple categories for Fido2 appears broken for windows as any attempt to login results in an error claiming Key not recognized, though fido2 keys test fine within the user's authentication portal.

Is anyone else seeing this after upgrading from 6.4.2 to 6.4.2.1?

Oddly for me, an android device enrolled as a fido2 key was able to authenticate itself to web service without this error

Rodney

If you found this post useful, give it a "Like" or click on "Verify Answer" under the "More" button.   This helps others.

Tags:

  • 0  

    Hello,

    Is this only for FIDO2 then? For the rest of the methods, does it work OK?

    If you recreate the chains, etc or the categories, is it still broken?

    This fix was introduced in 6.4.2, so it would be very strange for 6.4.2.1 to break it. Not saying is not happening, it is just very unusual.

    I would advice also on opening a ticket with support, for better tracking of the issue.

    Thanks.

    Regards,

    Luciano Testa

  • 0   in reply to   

    I have an open ticket 02758158

    Don't know if other multiple categories methods are affected, will try multiple appcodes later.

    This worked fine previous to 6.4.2.1

    Rodney

    If you found this post useful, give it a "Like" or click on "Verify Answer" under the "More" button.   This helps others.

  • 0   in reply to   

    Thanks. I'll keep an eye on the ticket.

  • 0

    Similar problem here.

    When I tested this, only the first FIDO2 key word; newly added keys did not work.

    When a colleague tested this, newly added keys worked, but they earlier added keys did not work any more

  • 0   in reply to   

    Is this fixed now ?

    David

  • 0   in reply to 

    Hello Mirko,

    Can you please open a ticket with Technical Support please? Right now Development has not been able to replicate this or duplicate the same behavior. It would help us understand how to repeat the problem and hopefully get to the root cause.

    Please mention the previous ticket so the engineer can link it to the internal Development investigation.

    Thanks.

    Regards,

    Luciano Testa

  • 0   in reply to   

    Hello David,

    It is not. Right now Development has not been able to replicate this or duplicate the same behavior.

    The feedback from development so far is that this seems related to categories. A test to check their theory would be to re-enroll the problem devices and see if the issue is resolved or if enrolling a new device in a different category invalidates the previously enrolled device.

    Thanks.

    Regards,

    Luciano Testa

  • 0 in reply to   

    Hello Luciano,

    I have opened ticket 02815290

  • 0   in reply to 

    Thanks Mirko.