OAuth2 issues authorizing to Box

[jposey]

I am using REST snaps to connect to and perform functionality in Box that are not available via Box Snaps. I am having trouble establishing my OAuth2 account. I have my ‘application’ setup in Box to connect to and have the client ID and secret all setup as well as the redirect URI to go to https://elastic.snaplogic.com/api/1/rest/admin/oauth2callback/rest.

When I try to authorize in the account creation in SnapLogic, I get prompted as expected by Box but am then redirected to a SnapLogic error after logging in. The error details state:

“Unable to decrypt property ‘$.settings.client_id’ with key: account-autogen”
“400 Bad Request”

Any ideas?

[aleung]

Do you get this page? Did you checked “Header authenticated” checkbox?

[jposey]

When clicking “Authorize” when creating/editing the user in SnapLogic, I do see the page you included. When I click “Grant access to Box” I am redirected to the URL, https://elastic.snaplogic.com/api/1/rest/admin/oauth2callback/rest which includes a “state” parameter and a “code” parameter. However, the page displays this error below.

{“query_string”: “state=hostname%3Dhttps%3A%2F%2Felastic.snaplogic.com%2Cinstance_id%#############################################&code=##################################”, “path”: “/api/1/rest/admin/oauth2callback/rest”, “response_map”: {“error_list”: [{“message”: “Unable to decrypt property ‘$.settings.client_id’ with key: account-autogen”}]}, “http_status”: “400 Bad Request”, “http_status_code”: 400}

Thanks again for your time and insight!

[andrew_holbrook]

@jposey, I’m curious, what use case are you trying to enable?

It is NOT fully tested nor feature complete, but I’ve been dabbling on a new Box snap pack to enable more of their API (with 136 snaps!!). I also implemented Box’s JWT account authentication, which allows you to authenticate as either a service account or as an “App User”. If you want to experiment with this let me know (although FYI I’m extremely busy the next two weeks so you may have to prod me).

I’ll also be at Box Works in the late morning and afternoon tomorrow if you’re attending that!

-Andrew

[jposey]

At a high-level, I am trying to upload documents to Box and populate a Box metadata template with values specific to the documents. Box Snaps allow me to upload the document and obtain the Box file ID, but I am having to leverage the Box APIs in order to do the metadata components.

Have you been able to successfully create an oAuth account do leverage within the REST snaps with Box? If so, I’d be interested in if you’ve seen issues similar to what I have asking about in this thread.

[andrew_holbrook]

Sorry, no I don’t need to use the REST snaps with Box. 😑