Box JWT auth: the app must be authorized in the admin console first

TL;DR

When Box JWT auth fails with unauthorized_client, check the admin console before debugging code. The app has to be authorized under Enterprise Settings, Apps by a Box admin; until then every token request fails.

Steps

1. When Box JWT auth fails with unauthorized_client, check the admin console before debugging code. The app has to be authorized under Enterprise Settings, Apps by a Box admin; until then every token request fails. Server auth also needs the app user created first, so confirm both pieces are in place.

When to use

You are seeing this: When Box JWT auth fails with unauthorized_client, check the admin console before debugging code. Use this skill when you run into "Box JWT auth: the app must be authorized in the admin console first".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Stack Overflow #43815989 (accepted answer, 7 votes): the asker's JWT server auth failed with unauthorized_client. The accepted answer: a Box admin must authorize the app under Admin Console, Enterprise Settings, Apps before JWT auth works. The code was fine; the app was never approved.

Verified resolution: When Box JWT auth fails with unauthorized_client, check the admin console before debugging code. The app has to be authorized under Enterprise Settings, Apps by a Box admin; until then every token request fails. Server auth also needs the app user created first, so confirm both pieces are in place.

Source URL: https://stackoverflow.com/questions/43815989/using-box-with-jwt-server-authentication