Just curious

[marksmithhfx]

I finally have a version of my application (note, its not a web app, just a regular compiled app) that I've migrated from LL access tokens to SL access tokens. I don't have it working with refresh tokens yet, that'll be the next step. But I've noticed that sometimes when I get asked to request a new access token (because the current one has expired), I click a few buttons on the confirmation screen and it sends me a new token without asking for my credentials (ie. no login screen). It happens in about 1 in 10 attempts. Is this typical work flow or is something weird going on? Thanks

[Здравко]

Hi @marksmithhfx,

I suppose, you haven't logged out of your Dropbox account in your web browser and haven't forced reauthentication (it's so by default). In this context - Yes, it's something normal. 😉

[marksmithhfx]

I see. Thanks

[Greg-DB]

@marksmithhfx That's correct, if you're already signed in, you won't be prompted to do so again. You can require sign in again by setting 'force_reauthentication=true' if necessary. Note that this is disruptive though (as it signs out the current Dropbox web session), so it should only be used for good reason.

Also, under certain conditions, if you're signed in and you've already authorized the app, you will not be prompted to explicitly click "Allow" to do so again. You can disable this behavior with 'force_reapprove=true' if you wish to.

[marksmithhfx]

BTW, is it possible to get biometric recognition for the Dropbox user authentication (facial or fingerprint) rather than monotonously type in your username and password (ie. I hate giving out my facebook or google account information, and I presume many other are too. It just ends up in someone's email list that bombs you with adverts). Biometric recognition would be much faster and less error prone. I am a long way off from getting refresh tokens working (for reasons I'd rather not go into) so I see this as a possible stop-gap measure to make life easier for my users. 

Thanks

Mark

[marksmithhfx]

Thanks on that point. I wasn't aware of any other sign-ins going on at the same time. But it's possible since I am on multiple devices and testing from multiple versions of the same app on each. Somewhere in there DB probably sees me as already signed in. That does explain the occasional unusual token hand-off. 

Appreciate the quick response. Cheers,

Mark

[Greg-DB · Accepted solution]

@marksmithhfx Dropbox doesn't offer an option like that, but you can share ideas here.