Authenticator: is "safe-auth:" always necessary?

In my desktop app, using FFI bindings, can I display a secret/pass dialog box and do the entire authorization process via FFI, with no necessity of the SafeBrowser?

I thought that the authorization process should always be handled by the “safe-auth://” plugin, but I just discovered that the safe_client_libs examples don’t use the authenticator to sign in/sign up in the network. Are they outdated or is this really possible?

Yes, because these libraries are the lower underlying API.

It is best only to use them for special cases though, otherwise the user has to enter credentials in multiple places. Also, they have to be willing to trust your app with their credentials.

1 Like