![]() So again, visitors to my website would be able to use this file uploader, like lets say they're uploading a profile picture for their profile page. Maybe I missed something elementary here, or possibly an online example. ' the below code is what I want to bypass, as in verifying the app permissions by loading a Dropbox verification page.ĭim authorizeUrl As String = "" + queryString2 AppendFormat("?oauth_consumer_key=", token) Signature = HttpUtility.UrlEncode(signature)ĭim requestUri As StringBuilder = New StringBuilder(uri.ToString) Here's some code: Dim appKey As String = "myappkey"ĭim nonce As String = oAuth.GenerateNonce()ĭim timeStamp As String = oAuth.GenerateTimeStamp()ĭim normalizedUrl As String = String.Emptyĭim signature As String = oAuth.GenerateSignature(uri, appKey, appSecret, String.Empty, String.Empty, "GET", timeStamp, nonce, 1, _ So I'm not wanting to use the api for every John Doe to grant permission and upload files to and from their own dropbox. The problem is I want end-users to be able to install the control, add their app/secret key to the control settings, and it's ready to go when the page loads. It appears that I have to first generate a token, verify the app, and then call along with the token. I've built a custom asp.net file upload control that supports server side storage and AWS S3, and I want to add Dropbox. ![]() ![]() ![]() I'm in the same boat this person is/was I believe: uploading files to Dropbox, bypassing authorization page? And you could get the Redirect URI there. To authenicate the Dropbox in your application, you need to register your application in the Dropbox platform first. I really hope this isn't a stupid question. Welcome to our Microsoft Q&A platform The WebAuthenticator API consists mainly of a single method AuthenticateAsync which takes two parameters: the authorization Url and the call back Url. ![]()
0 Comments
Leave a Reply. |