0

We've been using the Forge DM webhooks for some time. But when we attempt to register an adsk.c4r/model.sync webhook, it gives a 401 error. We have all of the "data"-related scopes set in our token.

{
  "id": "22c519a4-0afd-46f5-b80e-3a718fe6b5a1",
  "status": 401,
  "code": "AUTHORIZATION_ERROR",
  "detail": [
    "User authorization was not defined for eso with system id: adsk.c4r and event id: model.sync"
  ]
}

Is there something else that needs to be authorized differently?

Matt
  • 1,043
  • 5
  • 8
  • Please check if your access token has both `data:read` and `data:write` scope and your client id is added as an activated app in the BIM360 account's custom integration tab. – Eason Kang Oct 07 '19 at 07:24
  • Eason - yes, we have done all of those things, and we still have the issue. – Matt Oct 07 '19 at 14:20
  • Matt, which kind of access token did you use, three-legged or two-legged? It seems to me this might be the difference between us. I used the two-legged access token to create a new C4R hook. – Eason Kang Oct 08 '19 at 02:08
  • One more thing to check: Please check if you can access other BIM360 API with the same client id added as an integration app of your BIM360 account. If you're encountering the same issue with the same client id, please follow this instruction here to do troubleshoot: https://fieldofviewblog.wordpress.com/2018/05/31/troubleshooting-tips-for-accessing-bim-360-docs-and-account-admin/ – Eason Kang Oct 08 '19 at 02:13
  • Eason, we tried with both two and three legged, out of interest, no luck. We typically use three legged. Using the same credentials, we can successfully call the api to create the various DM webhooks, just not that webhook. – Matt Oct 08 '19 at 02:41
  • Ok... that sounds strange. It might be not possible, but one more thing to check: have you activated the Design Collaboration service for the project that contains the input folder urn you passed in the request body? – Eason Kang Oct 08 '19 at 08:05
  • Eason - I'm not sure if our previous test had something wrong, but now we can see it working when using 2-Legged OAuth. It still doesn't work with 3-Legged. Not ideal, but we'll make it work. – Matt Oct 08 '19 at 15:13
  • Glad to hear 2LO is working for you. It seems not to support 3LO access token creating c4r related event, I received the same error message while passing 3LO token. I'm checking with our engineering team, and will get you back A.S.A.P. – Eason Kang Oct 09 '19 at 06:30
  • Matt, I got the confirmation from our engineering team, 3-legged access token is not supported for creating c4r related hook currently unfortunately. Is there special reason that you want crest hooks with 3LO token? – Eason Kang Oct 09 '19 at 23:54
  • We avoid 2LO entirely, because we feel that- in the AEC world where there are always multiple companies involved, that 2LO gives you too many permissions, and what we really want is to be operating “as a user”. Jim Q knows my rant on this topic. – Matt Oct 10 '19 at 00:14

1 Answers1

0

My apologies for the delay, we have some backlog in the work queue. After discussing with our engineering team, the C4R related hooks support 2LO access token only currently. Sorry for the bad news.

Eason Kang
  • 6,155
  • 1
  • 7
  • 24