Whenever a secured service endpoint is accessed, it triggers the authentication and authorization of workflow with the final destination endpoint. As a result, an access token is obtained with a specific expiry. The access token is internally cashed for the expiry interval by the platform. The cached access token is used for all subsequent calls to this service. A new token is always obtained implicitly at the end of expiry time and with the refresh token which makes the overall process more automated and hidden from the frontend.