新しいBoxサポートサイトへようこそ。 変更点の詳細はこちらをご確認ください .

Accessing collaborating folder with DEVELOPER-TOKEN and not with APP-USER

新規投稿

コメント

3件のコメント

  • LoCortes

    Hello there ,

     

    The developer token is using your user, so you already have access by default.

     

    that APP-User has been added as a collaborator on that folder? think that it is like any other managed user, it has to be invited to be able to see and upload files.

     

    Regards,

    0
    コメントアクション パーマリンク
  • guyso

    Hello ,

     

    thank your first for your answer.

    I am not admin on that folder because it belongs to a partner company.

    Like mentioned the APP-USER was created programmatically to shortcutting the configuration in the UI.

    So the APP-User is not manually invited. Could I do it for a such folder programmatically?

     

    I have also another question concerning JWT and OAuth2 because i use it:

    1- What is the difference between the ENTERPRISE-TOKEN and APP-USER-TOKEN?

    2- What token should be used in this case for accessing the collaborated folder?

     

    Kind Regards

    0
    コメントアクション パーマリンク
  • LoCortes

    Good morning ,

     

    yesterday I answered your message but you deleted one of the two repeated messages so the forum gave an error and my answer was lost hehehe and to be sincere, I thought to do it again but yesterday flew... so, today trying again.

     

    App-users can be created and assigned as collaborators through the API but will depend also on the permissions that the application / service account has. Also, you could do the other way around. Create folders with the service account or the app-users and invite the managed users to there.

     

    About the other two questions (yesterday were three, weren't they? :))

     

    1- This is a very common question and it is related to this thread: https://community.box.com/t5/Box-Developer-Forum/quot-Service-account-quot-vs-quot-app-user-quot/m-p/38592#M2557. Enterprise-token is a token using the service account and the app-user-token is using regular app-users.

    2 - The answer is an ambigous "it depends" 🙂 I mean... the service account is like the "father" or "mother" of all the app-users created on that application. So, I would use that account (enterprise-token) as a powerful resource for administrative tasks (if any), maybe ownership of created folders within the application and in case that only one single user is enough for you. If you want / need to have several app-users due to limit api calls, one to one mapping with real users or something like that, then the token to be used is the app-user-token.

     

    Hope this time arrives 🙂 and more important helps!

     

    Regards

    0
    コメントアクション パーマリンク

サインインしてコメントを残してください。