We’re Still Here to Help (Even Over the Holidays!) - find out more here.
Forum Discussion
Solved
DropboxOAuth2Helper GetAuthorizeUri removing port from redirecturl?
When using the DropboxOAuth2Helper.GetAuthorizeUri - we pass in the following params:
var response = DropboxOAuth2Helper.GetAuthorizeUri(OAuthResponseType.Code, ClientId, redirectUrl, state);
Where the redirectUrl is a link similar to the following:
https://my-site.domain.com:443/rest-of/the/url/auth-complete
However the response that comes from it doesn't include the '443' and that seems to be causing issues when trying to authenticate.
Ie. response is as follows (example):
https://www.dropbox.com/oauth2/authorize?response_type=code&client_id=y7c53f1wctrfmw8&redirect_uri=https:%2F%2Fmy-site.domain.com%2Frest-of%2Fthe%2Furl%2Fauth-complete&state=MxuufKLcqtGRLQLDNgaYnsvowunHhvfnpoKZKEIvamanPmwvIMTMoqhDBpjH WBsddOiTEeDvfoEPgfEzolugXskJnzcOpQyoMtmRkkhqbCqmsaIizwQpBzvSeEsJbjMPXfZapCnvUIKfgToizDMnbxRPhzPXnYpUUOjFYhphBDHduROpUusecDHIRJSnYipvtrlQITt
Does anyone know what could be causing this? Is this an inherent part of how this function should work?
The Dropbox .NET SDK builds a Uri from the redirectUri string you provide, using the Uri Constructor. The Uri Class canonicalizes URIs, including:
"Removes default and empty port numbers."
The "443" port is default for SSL/TLS, so it's implied by "https://" and shouldn't be necessary.
Can you elaborate on the issues you're running in to with it omitted though?
5 Replies
- Greg-DB
Dropbox Community Moderator
The Dropbox .NET SDK builds a Uri from the redirectUri string you provide, using the Uri Constructor. The Uri Class canonicalizes URIs, including:
"Removes default and empty port numbers."
The "443" port is default for SSL/TLS, so it's implied by "https://" and shouldn't be necessary.
Can you elaborate on the issues you're running in to with it omitted though?
Hi Greg, thanks for the reply!
Since the GetAuthorizeUri method seemed to be removing the 443 it was a mismatch between the redirect url sent in there and the one we were sending into the ProcessCodeFlowAsync method - although to us, the url we were sending into both of them was the same. Once we also removed the 443 from the PCFA method, we were able to authenticate with dropbox.
The removal of the default port was not inherently obvious in these docs when we went looking for what was happening: https://dropbox.github.io/dropbox-sdk-dotnet/html/M_Dropbox_Api_DropboxOAuth2Helper_GetAuthorizeUri.htm
- I should specify that the error we were getting was:
An unhandled exception has occurred: invalid_grant (1fff7674)
Dropbox.Api.OAuth2Exception: invalid_grant - Greg-DBI see, thanks for the information. In that case, you should register the redirect URI without the port. I'll ask the team to clarify this in the documentation.
- Yes we have, thank you!
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
