• Resolved wpprup

    (@wppraesenz)


    Hello,
    I am really thankful that you integrated passkeys now, as already said. I am experiencing the following behavior:
    In the log in window to the admin backend I click the button to log in with a passkey. Then the window changes to only the username field and this I fill, then pressing the log in with a passkey-button. (I think up to here it is the normal process.)
    Instantly I see two error messages and despite that the Windows Hello request for the fingerprint appears (the regular behavior). Then I give the fingerprint, but it does not log in.
    When I repeat the process, I can log in – just like it should be.
    The error massages obviously seem to react faster than Windows Hello can react and they prevent the log in, I think. Perhaps they could be a bit more patient, then everything would be fine… 😉

    The picture is but not consistent. On one website the process (always done as described) works fine, on three sites not. Consistent is but the behavior per website.

    Error messages:
    Website one:
    “Authentication ceremony was sent an abort signal
    The authenticator was unable to process the specified options, or could not create a new assertion signature” – second trial successful

    On another website:
    “Authentication ceremony was sent an abort signal
    The operation either timed out or was not allowed. See: https://www.w3.org/TR/webauthn-2/#sctn-privacy-considerations-client ” – second trial successful

    On a third website only:
    “Authentication ceremony was sent an abort signal” – log in with the first trial here successful.

    Perhaps you can improve the process using these informations. Thanks.
    (For more information about the URL of admin pages please give me an email address)

    • This topic was modified 2 months, 4 weeks ago by wpprup.
    • This topic was modified 2 months, 4 weeks ago by wpprup.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    Hello @wppraesenz !

    Thank you for reporting this! This is the first time seeing such errors, and we would definitely would like to check further and see if this is actually something causes by our plugin or by an interaction with some other plugins or custom code from the site.

    Feel free to email us at support@melapress.com with a note about this thread, so we can correlate, and we’ll surely get back to to you as soon as we can.

    Looking forward to your update!

    Thread Starter wpprup

    (@wppraesenz)

    I think I could pin down the reason. It is not a plugin, it is the password manager “Roboform” (here as a browser extension) I am using that interferes in the login process. When I fill in the user name manually, the process runs correctly. I think I have to contact their support… 😉

    • This reply was modified 2 months, 3 weeks ago by wpprup.
    Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    Thanks for the update @wppraesenz !

    Sure, keep us posted on the outcomes, as this might indeed be an interesting one which might as well help others who might be facing similar issues.

    Have a great day!

    Thread Starter wpprup

    (@wppraesenz)

    Preliminary answer from the RF support:
    “Thank you for your message.

    Your ticket has been escalated to our senior support team for further review.
    They will investigate the issue in detail to determine the root cause and next steps.
    Please note that escalations can take additional time depending on the complexity of the issue.

    Thank you for your patience and understanding as we work diligently to resolve this matter.”
    Let´s wait… 🙂

    Thread Starter wpprup

    (@wppraesenz)

    Hello,
    I checked again and the error continues to be without Roboform. And I contacted the RF support and they confirmed after some checks on my side (deactivating RF etc.) that it is your plugin that causes the problem. Although one can live with multiple login trials it would certainly be good if this was solved. Thank you very much.

    Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    Thank you for the update @wppraesenz !

    Would it be possible to contact us at support@melapress.com while referencing this ticket? We can exchange more (sensitive) information over there and maybe try to reproduce this and see if it’s indeed something we can fix from our sided? We’re more than happy to take another look, so feel free to reach out!

    Many thanks!

Viewing 6 replies - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.