We do not actively update the access token. Developers initiate the access token update operation. There are the following situations:
- You can configure the access token validity period in the developer backend. It is permanent by default. In subsequent login processes, you do not need to request an access token from Nexconn again; your App Server directly provides the previously saved access token.
- After refreshing the App Secret in the console, the previously obtained access tokens become invalid. You need to use the new App Secret to generate a signature and obtain new access tokens.
- The App Server actively calls the Nexconn API to get an access token. You can get an access token multiple times for the same user ID. The access token can be used normally within its validity period. After the access token expires, it becomes invalid, and you need to get a new one.
Related documentation:
Why doesn’t the client support fetching Token, and why must Token be requested from the server?