Showing results for 
Search instead for 
Did you mean: 

OAuth2 issues authorizing to Box

New Contributor II

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

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?


Contributor III

In Box:
Configuration > OAuth 2.0 Redirect URI =

Integration > Web App Integration > Client Callback URL =[your Authorization Token]

In Snaplogic:

OAuth2 Endpoint: Box - Free Online File Storage, Internet File Sharing, Access Documents & Files Anywhere, Backup Dat...
OAuth2 Token:

Hope this help!

New Contributor II

Thank you for the response. I am new to the concept of the Box Integration and am curious if this is necessary. The error I am receiving is while trying to create/authorize a new REST OAuth2 Account in SnapLogic to use when calling Box APIs via the REST Snaps.

Is your response indicating that I need to create a task for my pipeline in order to get the URL and bearer token for the web integration setup? I would like to be able to create the account and run it locally in SnapLogic prior to moving on to the task creation.


Contributor III

No it isn’t necessary but just in case you want to.

New Contributor II

OK. Thanks again for your time and responses. I have referenced your original response and checked my settings in both SnapLogic and Box.

For the Box settings, the Redirect URI looks correct in the application. I have not created a triggered task for this pipeline, so I have not setup anything in the web app integration settings.

For SnapLogic, I have similar oauth2 settings in my account settings - the only difference being that I am pointing to a development instance of Box which uses a sub-domain of

When I go to authorize the account in SnapLogic, I am prompted to login to Box as expected, however am still receiving the error I quoted in my original post.

Could I be missing something in my administration configuration in Box? Do I need to explicitly grant some type of add the SnapLogic application somewhere? I can connect to the APIs just fine when using the Box developer token.