Yes. SAP Open Connectors does perform the x-dropbox-signature
validation for handling Dropbox events.
Yes. SAP Open Connectors does perform the x-dropbox-signature
validation for handling Dropbox events.
We are in the process of normalizing the documents hub even further, but there are always a few unique API provider differences and the 'ID' used to make a GET by the root folder ID is one such difference.
Currently the following values can be used in these connectors to make GET calls directly against the root folder by ID (for example, GET /folders/{id}/contents
or GET /folders/{id}/metadata
).
0
. For example GET /folders/0/contents
.%252F
. For example, GET /folders/%252F/contents
.root
. For example, GET /folders/root/contents
.root
. For example, GET /folders/root/contents
.top
. For example, GET /folders/top/contents
.If you do not permanently delete Dropbox files, they remain in your Trash folder and generate an UPDATED
event type if they are re-created.
Dropbox includes a refId
for certain APIs. This is the actual ID of the file sent back from Dropbox. It can be used as the ID
with all API calls with the exception of GET /folders/{id}/contents
.
The GET /folders/{id}/contents
endpoint does not support the refId
at this time.
In Dropbox, file links can only have one shared link at a time for a given file. This means if you generate a file link that has the default visibility of 'PUBLIC' then any subsequent calls to GET /files/{id}/links or GET /files/links will simply return the existing PUBLIC link rather than generating a new link. This is true even if you are trying to generate a new link with a different level of access such as visibility=TEAM_ONLY. Therefore if you need to create a new file link for any reason you will first need to revoke/delete the original file link and then generate a new file link.
Within the Dropbox connector, this is accomplished by:
{
"cloudElementsLink": "https://api.openconnectors.us2.ext.hana.ondemand.com/elements/api-v2/external/documents/files?key=XXXXXXXXXX",
"providerViewLink": "https://www.dropbox.com/s/XXXXXXXXXX/yourFile.pdf?dl=0",
"providerLink": "https://www.dropbox.com/s/XXXXXXXXXX/yourFile.pdf?dl=1" }
{
"cloudElementsLink": "https://api.openconnectors.us2.ext.hana.ondemand.com/elements/api-v2/external/documents/files?key=YYYYYYYYYY",
"providerViewLink": "https://www.dropbox.com/s/YYYYYYYYYY/yourFile.pdf?dl=0",
"providerLink": "https://www.dropbox.com/s/YYYYYYYYYY/yourFile.pdf?dl=1" }
If you enable the Document Hub Tagging (document.tagging
) configuration parameter with certain connectors from the Documents hub, the paths and tags for any documents accessed will be stored in the SAP Open Connectors database in clear text. Affected connectors include a mention of this in their respective descriptions of the parameter.
Documents connectors affected include:
See our Data Protection & Privacy documentation for specifics about our data storage and security policies.