Access Token Expiration

OAuth 2.0 JWT access tokens can have an expiration time specified through the ‘exp’ claim. The EMS server enforces access token expiration by disconnecting the associated EMS client (or EMS server).

In order to minimize connection disruptions due to access token expirations, the EMS server periodically examines the access tokens of all connected EMS clients to check for upcoming expirations. If an access token is nearing the end of its lifetime, the EMS server will send a request for re-authentication to the client. This provides the client the opportunity to procure a new access token and authenticate with the EMS server again before the current access token expires.

If an EMS client (or EMS server) obtained its access token using one of the supported grant types, upon receiving a re-authentication request from the EMS server, it will automatically procure a new access token from the OAuth 2.0 authorization server and re-authenticate itself with the EMS server without any connection disruption.

If an EMS client obtained its access token through other means (see Access Token Expiration), it will need to be told how to handle the re-authentication request from the EMS server via a user-defined callback. Refer to the relevant EMS client API documentation for details.