在 BIM360 OSS 中为对象创建签名 URL [英] Create Signed URL for Object in BIM360 OSS

问题描述

我正在尝试为由 BIM360 OSS 内的 Webhook 触发的设计自动化工作流设置签名 URL.如果添加了文件，则 webhook 会触发端点以启动设计自动化.网络钩子正在工作.设计自动化也在发挥作用.如果我尝试将两者都连接起来，就会出现问题.我#m 正在尝试创建文件的签名 URL，如 Petr Broz link stackoverflow 中建议的那样.

I'm trying to set up an Signed URL for an Design Automation Workflow which is triggered by an Webhook inside of the BIM360 OSS. If a file is added the webhooks triggers an endpoint to start a Design Automation. The webhook is working. And the Design Automation is working too. The Problem occurs if i try to wire both up. I#m trying to create a Signed URL of the File like suggested in this post from Petr Broz link stackoverflow.

要使用此 API，需要使用由 2-Legged-Auth 获得的令牌，该令牌可与所有必要的范围一起使用.在 Webhook 的响应中是文件夹和版本的 ID.API 正在识别 ID.问题出现在此端点创建签名 url 的响应中:https://developer.api.autodesk.com/oss/v2/buckets/:bucketKey/objects/:objectKey/signed

To use this API it is requierd to use an Token which is obatined by 2-Legged-Auth which is working with all necessary Scopes. In the response of the Webhook is an ID for the Folder and Version. The API is recognizing the ID. The problem occurs in the response of this endpoint to create the signed url: https://developer.api.autodesk.com/oss/v2/buckets/:bucketKey/objects/:objectKey/signed

我使用 wip.dm.emea 作为存储桶，因为该文件存储在 EU BIM360 OSS 中.

I'm using the wip.dm.emea as bucket because the file is stored in the EU BIM360 OSS.

响应是403 Forbidden:

{
    "reason": "Only the bucket creator is allowed to access this api."
}

是否可以像本例中那样获取文件 ID 伪造如何下载文件?因为这个解决方案需要一个 3-Legged-Auth 流程，这对于一个完整的自动化来说是不可能的.

Is it even possible to get the File ID like in this example Forge how to Download File ? Because this Solution requires a 3-Legged-Auth Flow which is not possible for a complete Automation.

让我质疑的是，您可以在平面 Forge 中实现此工作流程.但在 BIM360 中，我无法控制系统创建的 Bucket！?

The thing which makes me question is, that you can achieve this Workflow in plane Forge. But not in BIM360 where i have no control over the Buckets that are created by the System!?

我认为这是 Forge API 和 BIM360 实现之间的架构不匹配！?将来会有解决方案吗?

I think this is an architectural missmatch between the Forge API and the BIM360 implementation!? Will there be a solution for this in the future?

最好的问候扬

推荐答案

很遗憾，我可以确认目前无法为您的 BIM360 存储创建签名 URL，如错误消息所述，端点需要存储桶所有者做这个操作，这就是现在的样子.但我同意你的看法，这应该是 Forge OSS 和 BIM360 实现之间的架构不匹配，并且我们的系统已经要求它，请保留CPOSS-1066"与我们一起检查进度.

Unfortunately, I can confirm that it's not possible to create a signed URL for your BIM360 storage currently, as the error message mentioned, the endpoint requires the bucket owner to do this operation, this is what it is now. But I agree with you that this should be an architecture mismatch between Forge OSS and BIM360 implementation, and it's already been requested in our system, please keep "CPOSS-1066" to check with us about the progress.

至于目前的方式，您可以保留 3 腿令牌并将其用于输出 Url 和 onComplete() 回调，我有博客文章 https://forge.autodesk.com/blog/upload-your-design-automation-output-file-bim360-docs 详细介绍了工作方式，希望对此时有帮助.

As for the current way, you can keep the 3 legged token and using that for the output Url and also in the onComplete() callback, I have the blog post https://forge.autodesk.com/blog/upload-your-design-automation-output-file-bim360-docs which details the way to work, hope it helps at this moment.

这篇关于在 BIM360 OSS 中为对象创建签名 URL的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！