title: Create Signed URL for Object in BIM360 OSS
body: <p>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 <a href="https://stackoverflow.com/a/54421189/9061456">link stackoverflow</a>.</p>
  
  <p>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: <a href="https://developer.api.autodesk.com/oss/v2/buckets/:bucketKey/objects/:objectKey/signed" rel="nofollow noreferrer">https://developer.api.autodesk.com/oss/v2/buckets/:bucketKey/objects/:objectKey/signed</a></p>
  
  <p>I'm using the <strong>wip.dm.emea</strong> as bucket because the file is stored in the EU BIM360 OSS.</p>
  
  <p>The response is a <strong>403 Forbidden</strong>:</p>
  
  <pre><code>{
      "reason": "Only the bucket creator is allowed to access this api."
  }
  </code></pre>
  
  <p>Is it even possible to get the File ID like in this example <a href="https://forge.autodesk.com/en/docs/bim360/v1/tutorials/document-management/download-document/" rel="nofollow noreferrer">Forge how to Download File</a> ?
  Because this Solution requires a 3-Legged-Auth Flow which is not possible for a complete Automation.</p>
  
  <p>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!?</p>
  
  <p>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? </p>
  
  <p>Best regards
  Jan</p>