Follow the steps below if you would like to leverage server authentication and verify your application's identity using a client ID and client secret.
Your client secret is confidential and needs to be protected. Because this is how we securely identify an application's identity when obtaining an Access Token, you do not want to freely distribute a client secret. This includes via email, public forums and code repositories, distributed native applications, or client-side code. If you would like to add more security mechanisms, we recommend using our standard JWT application type.
When making your API call to obtain an Access Token, your request body needs to contain your client ID and client Secret. Set the grant_type
to client_credentials
.
If you would like to authenticate as the application's Service Account:
box_subject_type
to enterprise
box_subject_id
to the enterprise IDIf you would like to authenticate as an admin or a managed user:
box_subject_type
to user
box_subject_id
to the user IDIf you would like to authenticate as any application user:
box_subject_type
to user
box_subject_id
to the user IDDuring authentication, you can encounter the following error:
Grant credentials are invalid [400 Bad Request] invalid_grant - Grant credentials are invalid
This error indicates either:
the client ID and client secret passed are incorrect or are not for the same application,
the box_subject_id
cannot be used based on the selected application access.
A CCG app with App Access Only can send in the box_subject_type
of enterprise
to authenticate as its service account, but it can't authenticate as a managed user or an admin.
to use a box_subject_type
of user
, your application should be configured to generate user access tokens in the Advanced Features section of the Configuration tab.
Once you make changes to the app settings, don't forget to reauthorize the application in the Admin Console.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4