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

问题描述

我正在尝试为设计自动化工作流设置一个签名URL，该URL由BIM360 OSS内部的Webhook触发.如果添加了文件，则webhooks会触发端点以启动Design Automation. Webhook正在运行.而且设计自动化也在工作.如果我尝试将两者都连接起来，则会出现问题.我试图创建文件的签名URL，如Petr Broz的这篇帖子中所建议的那样链接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禁止访问:

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

是否甚至可以像本例中那样获取文件ID，伪造如何下载文件? 因为此解决方案需要3级授权流程，所以对于完整的自动化而言这是不可能的.

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中却没有，我无法控制系统创建的存储桶！?

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()回调中使用博客文章

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屋！