Box account with our own Box connected app

[sg_sripathi]

Hi,

Today while creating the Box account, SnapLogic internally uses a connected app in Box (client_id=4y9mpks2hql3xchpudijkct1vfhwwklx), it is not possible to override this with our own connected app.

Due to this at the Box side all the API calls are registered against “Snaplogic app” connected app. There is no way to track which project in SnapLogic is actually using the APIs. In our case we have many projects uses Box, each have their own quota of Box usage, since SnapLogic is using same connected app at the Box side we are not able to govern the Box usage accurately.

Is there a way or implementation plan in progress to allow feed in out own client_id for Box account?

Regards,
Sripathi

[sg_sripathi]

Anyone to comment, feel a little lonely here 🙂

The issue is also related to how Box licenses are today, the API calls are a commodity, hence knowing which snaplogic project use how much APIs on the Box side is becoming a necessity. All API calls grouped under “SnapLogic app” is not sufficient.

Regards,
Sripathi

[robin]

@sg_sripathi this weekend’s August 2019, 4.18 release includes the option to use a Box Service Account.

This will mitigate API usage concerns when using a SnapLogic-registered OAuth application for the standard Box Account.