Level up your Box knowledge with brand new learning paths on Box University. Visit training.box.com to get started

0Auth Help with FME

New post

Comments

4 comments

  • BobFlynn-IU

    ,

     

    You will have a greater chance at success posting this to the Box Developer Forum. We're just a bunch of end users and admins.

     

    Bob

    0
    Comment actions Permalink
  • Adam_B

    Hi Bob, thanks. Looks like someone went ahead and moved the thread for me!

    0
    Comment actions Permalink
  • Adam_B

    Hi everybody,

     

    Didn't find an answer here. Worked with my DevOps admin to setup proper 0Auth credentials via Box (Client ID, Client Secret Key, and redirect to localhost). I had done it correctly for a local FME user, but something was missing to get FME setup with Box in server-side/multi-user environment. The Client ID & Client Secret Key were correct, but the localhost redirect would not work.

     

    Redirecting to the FME Server 0Auth page did not work either, until SSL encryption was running properly on both the machine (Windows Server) and FME Server. I do not know the specifics of that setup, but after getting SSL encryption running, we were able to successfully redirect Box 0Auth requests within FME to the FME Server's 0Auth page. I know this may not be the step by step instructions someone reading this may be hoping for, but I hope it leads you in the right direction.

    0
    Comment actions Permalink
  • matt-lindsay

    Hi ,

     

    It's interesting that you've been using the Box API with FME. I develop with the Box API in nodejs normally, but I'm testing the feasibility of using FME Desktop for one off content upload / processing jobs. Are you able provide details of how you configured the web service in FME Desktop please?

     

    Thanks Matt.

    0
    Comment actions Permalink

Please sign in to leave a comment.