Dropbox OIDC error "Use HTTP POST requests instead of GET to access Dropbox API's" #8270
-
|
Hello All, Setting up OIDC authentication to Dropbox using in my export OIDC_CLIENT_ID=(Dropbox App Key)
export OIDC_CLIENT_SECRET=(Dropbox App Secret)
export OIDC_AUTH_URI=https://www.dropbox.com/oauth2/authorize
export OIDC_TOKEN_URI=https://api.dropboxapi.com/oauth2/token
export OIDC_USERINFO_URI=https://api.dropboxapi.com/2/openid/userinfo
export OIDC_USERNAME_CLAIM=username
export OIDC_DISPLAY_NAME=DropBox
export OIDC_SCOPES="openid profile email"This seems to work but the authentication fails with the error: {
"error": "Failed to parse response from https://api.dropboxapi.com/2/openid/userinfo. Expected JSON, got: Error in call to API function \"openid/userinfo\": Use HTTP POST requests instead of GET to access Dropbox API's",
"level": "error",
"message": "Error during authentication",
"stack": "InternalServerError: Failed to parse response from https://api.dropboxapi.com/2/openid/userinfo. Expected JSON, got: Error in call to API function \"openid/userinfo\": Use HTTP POST requests instead of GET to access Dropbox API's\n at InternalError (/app/code/build/server/errors.js:36:34)\n at request (/app/code/build/server/utils/passport.js:79:37)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async OAuth2Strategy._verify (/app/code/build/plugins/oidc/server/auth/oidc.js:57:23)"
}Which I guess is simply because Dropbox is expecting POST requests per their documentation? Should I set this up differently to make OIDC to Dropbox work? Perhaps some obvious error in my setup that I overlooked? Or is this something that the Outline devs need to take a look at? Brian |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
Yep it seems that way – Dropbox is not properly following the spec which should allow a |
Beta Was this translation helpful? Give feedback.
-
|
Hello Tom, The idea is to use Outline as companion app to our small-team Dropbox document storage. Since Outline's cloud hosted version is limited to identity providers we don't use, I took a look at the self-hosted option. That works for us, embedding Dropbox content works perfectly, but the lack of a shared security context with Dropbox makes it difficult to align document and content permissions. I understand a 3rd party IdP can solve this, but it requires a more expensive Dropbox tier and adds costs and complexity without other benefits for us. Is there any chance that Dropbox OIDC support could be added to the roadmap? For example as part of the self-managed Business tier subscription? The effort might be limited and Dropbox is not exactly a niche platform. In any case the effort of the dev team is really appreciated. It's a great product that runs circles around Dropbox's own solution and the other tools I reviewed. Best regards, |
Beta Was this translation helpful? Give feedback.
-
|
If the only difference is the HTTP method it's not hard to add an exception/mapping here in the code, there might be others in the future. |
Beta Was this translation helpful? Give feedback.
-
|
Potential code change here: |
Beta Was this translation helpful? Give feedback.
-
|
Hello Tom, That is excellent news, thank you very much for that. I'll keep an eye on the releases and test it when available. Best regards, |
Beta Was this translation helpful? Give feedback.
-
|
You can try |
Beta Was this translation helpful? Give feedback.
Potential code change here:
#8282