When using an OTP, the common worflow is for the client applications to display an OTP field, let users open their authenticator app, copy the OTP and then fill it in the field.
When the authenticator is on the same device than the client application, this could probably be automated a bit.
I can think of another worflow: user could click on a button near the OTP field that would automatically open the authenticator app, the authenticator app would display a consent dialog and would then redirect to the client app.
Redirecting from the client to the authenticator app could be done with a dedicated URL scheme, or by extending "otpauth://.
Redirecting back from the authenticator app to the client could be done by passing a redirect_uri parameter in the initial redirection, in the fashion of OAuth2 redirections.
The main benefit for this is that it would help non tech savvy people to use authenticator app with less friction: no codes to deal with, no copy/pasting.
What do you think?
When using an OTP, the common worflow is for the client applications to display an OTP field, let users open their authenticator app, copy the OTP and then fill it in the field.
When the authenticator is on the same device than the client application, this could probably be automated a bit.
I can think of another worflow: user could click on a button near the OTP field that would automatically open the authenticator app, the authenticator app would display a consent dialog and would then redirect to the client app.
Redirecting from the client to the authenticator app could be done with a dedicated URL scheme, or by extending
"otpauth://.Redirecting back from the authenticator app to the client could be done by passing a
redirect_uriparameter in the initial redirection, in the fashion of OAuth2 redirections.The main benefit for this is that it would help non tech savvy people to use authenticator app with less friction: no codes to deal with, no copy/pasting.
What do you think?