Skip to main content
Question

Autodesk Docs integration fails

  • November 26, 2025
  • 4 replies
  • 29 views

jkr_wrk
Influencer
Forum|alt.badge.img+35

As of today we get a message trying to login to Autodesk with the FME web connector.

I think we use the settings provided by the Autodesk integration:

Client ID: 9YJwNVyykGTllW87Y45yDUGLRvvOmVhM

Client Secret: dont know

Redirect URI: https://127.0.0.1:443

Auth Url: https://developer.api.autodesk.com/authentication/v2/authorize?response_type=code&scope=data:read data:write

Retrieve Token: https://developer.api.autodesk.com/authentication/v2/token

Request format: code=[CODE]&redirect_uri=[REDIRECT_URI]&grant_type=authorization_code

Refresh token: https://developer.api.autodesk.com/authentication/v2/token

Format: refresh_token=[REFRESH_TOKEN]&response_type=refresh_token&grant_type=refresh_token&scope= data:read data:write

 

When using a custom app created in Autodesk Forge I am able to connect with these settings (only changing the client_id and client_secret.

 

Also…

Would there be any instructions about creating a server-to-server integration in Autodesk Construction Cloud?

 

 

 

 

 

 

4 replies

desiree_at_safe
Safer
Forum|alt.badge.img+16

Hi ​@jkr_wrk!

From the details you shared so far, it looks a lot like an issue we’ve noticed with the Autodesk API restricting FME’s embedded browser, but just to confirm, what specific build of FME are you using?

If that’s the case, a quick and long term fix would be to use the external browser, available in FME 2025.2+ which is already available on the downloads page! (Proxy Redirect worked well from my testing)

There’s currently a workaround for the embedded browser with FME 2025.1.3.1+ where changing the User Agent (within the Manage Web Services dialog) to System Default will also bypass this error. 

 

Hope this helps! 🙂

 

Also as a side note, I still have an internal case filed for this issue! [INTERNAL REF: FMEENGINE-88785]


jkr_wrk
Influencer
Forum|alt.badge.img+35
  • Author
  • November 28, 2025

The notification in 2025.1.3 changed but the error persists.

In 2025.2 the error changed from none descriptive to pretty clear:

 

When switching to the “Proxy Redirect” setting it worked, thanks. But this is not available within 2025.1.3 or older versions. We cannot change to 2025.2 instant so how could we solve it for older versions?

 

 

 

 


jkr_wrk
Influencer
Forum|alt.badge.img+35
  • Author
  • November 28, 2025

The fix for FME 2025.1.3 and earlier would be to change the redirect uri to https://fmeauth.safe.com/v1/oauth2

 

While it it possible to have multiple redirect_uri’s per App. Safe Software probably removed the old one and replaced with the new one.

But the Autodesk Packages is still installed with the default old redirect uri as far as I can test (removing and reinstalling)


desiree_at_safe
Safer
Forum|alt.badge.img+16

When checked yesterday, I was was able to authenticate with the embedded browser in 2025.1.3.2 - Build 25646, but I understand the team is currently working on it and somethings may have changed between then and now.

I’ll add this context to the internal ticket. I understand upgrades are tricky and definitely something you can’t/shouldn’t rush.

 

As for the second part of your original question, about the server-to-server connection, I was digging into it a bit more, and it looks like the Autodesk package doesn’t currently support it, but it looks a really great enhancement!!

I encourage you to click this link and submit an idea capturing your product improvement suggestions. Other FME Community users can upvote ideas, and our product team reviews them for future inclusion.

Technically, you can create this connection in FME Form, you don’t really get all the great functionality already built into the package! 🙂 I can see who this would be great for FME Flow processes