• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 95 subscribers
  • Views 3203 views
  • Users 0 members are here
Options
Related
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

Web - 6.1 - Login via Formfill by Passwordmanager

Martin.Guckes
over 8 years ago

Hi there,

i've a question regarding the possiblility to make the web of 6.1.x more accessible for the formfill of an PW-Manager for example.

The situation is the following. The StandardWeb synchronizes each value of an field by an XHR-Request which is generated mostly by the onblur-Event of an HTML-Entity in the browser.

Everything is fine. The server has the same information like the client. But sometimes it takes some milliseconds.

The Problem i have is when i use a tool which automatically fills some fields and send an submit, the information is possibly not on the serverside. Especially by using the login via a password manager this can be a problem because if the Tool "hits" the Login button to fast the information is not on the serverside and the login is not successfull.

Is ist possible to avoid this behavoir for the login so that the userid and the password are submitted in the request which is created by the Login-Button? Or is there an possibility to deny the pw-manager click on the login button until the userid and the password are on the serverside?

Are there other possibilities to get not in trouble with this asynchronos logic? To set a delay in the Password manager is a problem because the time can differ by the country where the application is used.

Thx in advance

Martin 

Parents
  • 0 over 8 years ago
    Hi Geraldine,

    this is a kind of what happens now. With automatically closing the error Message from the Authentification and repeat. This confuses some users so i would prefer a solution without an error message for the end user and an exception in the log.

    There are currently two considerations:

    1st: deactivate the login button until the values in the collection are not null or empty.

    2nd: set an hidden pixel when both values are not null or empty

    Both are less than optimal :-)

    Do you have another considerations?


    Thx
Reply
  • 0 over 8 years ago
    Hi Geraldine,

    this is a kind of what happens now. With automatically closing the error Message from the Authentification and repeat. This confuses some users so i would prefer a solution without an error message for the end user and an exception in the log.

    There are currently two considerations:

    1st: deactivate the login button until the values in the collection are not null or empty.

    2nd: set an hidden pixel when both values are not null or empty

    Both are less than optimal :-)

    Do you have another considerations?


    Thx
Children
No Data