We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
SosiOne
9 months agoExplorer | Level 4
codeVerifier not initialized in dbx.auth.getAccessTokenFromCode
Hi! I am setting up Dropbox OAuth in an Electron app, and I got the part with generating a redirect URL, opening it in a browser window and letting the user log in working. I can then successfull...
- 9 months ago
SosiOne wrote:... But if I look at where the error comes from, there is a check:
if (!this.codeVerifier) {
throw new Error('You must use PKCE when generating the authorization URL to not include a client secret');
}so I suppose that something is not set up correctly here.
...
Hi SosiOne,
Yes, exactly - there is something wrong. 🙂 You are probably unaware how PKCE works. Key moment is to avoid a "man in the middle" during authorization. That's why pair of values are generated - code challenge and code verifier. They are passed during first and second step of the process. Only you (your application actually) is aware about values. In such a way the "man in the middle" (potential attacker) cannot stеal the authorization (possible stealed code is unusable, as in your case). The state should be kept during the process, so the values don't get lost, but you're using new object on the second step - for sure your codeVerifier is lost now (it's clear). Probably you don't understand that you have tried to impersonate yourself as attacker unintentionally (even the impersonation is incomplete and that's why consistency check catch it). Even if you pass that check the server will stop you - the value wouldn't match.
Restructure your code, so the client object stay from the start to the end of OAuth flow and use the same object in both steps. 😉
Hope this helps.
Здравко
Legendary | Level 20
SosiOne wrote:... But if I look at where the error comes from, there is a check:
if (!this.codeVerifier) {
throw new Error('You must use PKCE when generating the authorization URL to not include a client secret');
}
so I suppose that something is not set up correctly here.
...
Hi SosiOne,
Yes, exactly - there is something wrong. 🙂 You are probably unaware how PKCE works. Key moment is to avoid a "man in the middle" during authorization. That's why pair of values are generated - code challenge and code verifier. They are passed during first and second step of the process. Only you (your application actually) is aware about values. In such a way the "man in the middle" (potential attacker) cannot stеal the authorization (possible stealed code is unusable, as in your case). The state should be kept during the process, so the values don't get lost, but you're using new object on the second step - for sure your codeVerifier is lost now (it's clear). Probably you don't understand that you have tried to impersonate yourself as attacker unintentionally (even the impersonation is incomplete and that's why consistency check catch it). Even if you pass that check the server will stop you - the value wouldn't match.
Restructure your code, so the client object stay from the start to the end of OAuth flow and use the same object in both steps. 😉
Hope this helps.
SosiOne
9 months agoExplorer | Level 4
Thank you! This indeed fixed my problem! 🙂
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
5,877 PostsLatest Activity: 12 months agoIf you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X or Facebook.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!