...
The BSN.cloud
...
authorization server supports the following token timespans:
Access tokens
...
have a
...
timespan of 5 minutes 30 seconds
Refresh tokens
...
have a
...
You must ensure that all of your applications and/or scripts are correctly handling and refreshing these tokens or you may find that they stop working correctly.
...
timespan of 12 hours
Sessions have a timespan of 24 hours
We reserve the right to change these timespans at any time.
Refresh token-based authentication workflow
...
The following flow diagram shows this flow:
...
First, the The client application authenticates with the BSN.cloud token endpoint by providing the credentials
If the credentials are valid, an access token and a refresh token are returned in the result
After that, the The client application makes an API call and must pass the access token
The API component validates the access token and allows access to the resource
Steps 3 and 4 can continue until the access token expires and the API signals this by returning an error response (this will be a
401or403status code)When the access token expires, the client application requests a new access token by providing the refresh token
The BSN.cloud token endpoint then issues a new access token and a new refresh token
Steps 3 through 7 keep on repeating repeat until the refresh token expiresWhen the refresh token expires, the , or is revoked, or the current session ends
The client needs to re-authenticate with the authentication server once again and the flow repeats from step 1.
...