| Panel |
|---|
| borderColor | #3D3D3D |
|---|
| bgColor | #F4F4F4 |
|---|
| titleColor | #3D3D3D |
|---|
| borderWidth | 0 |
|---|
| titleBGColor | #3D3D3D |
|---|
| borderStyle | solid |
|---|
|
ON THIS PAGE |
The BSN REST API uses the OAUTH 2.0 framework to handle client authentication. This page describes how to build BSN token authorization into a client application.
| Note |
|---|
|
The BSN user model distinguishes between "persons" and "users": - A "person" is tied to a single set of login credentials, but is not exclusively linked to any one network (each network is an independent set of users, files, presentations, etc.).
- A "user" is an instance of a person that is associated with a single network.
This system allows persons who belong to multiple networks to log in to them using a single set of credentials. In many cases, it also requires two token-authentication requests, as described below. |
...
| Note |
|---|
|
The expires_in value may be changed on the server at any time, or it may be randomized on each authentication return. Therefore, the token expiration time should not be hardcoded on the client application; the application should store the expires_in value along with the Access/Refresh calculate a new token-refresh interval on every return. |
Example Requests and Responses
Person Authentication Request
...