Skip to main content

Hi,

We are having a similar issue to the one mentioned here. We're using the Node SDK, and migrated from password authentication to JWT authentication.

After reading the docs, it seemed that JWT authentication did not require any accessToken or refreshToken management, and we would just maintain a login state without any issues... but that does not appear to be the case.

We first received "Refresh token is missing" errors - and enabled refresh tokens in the app. This fixed the issue for now.


Here's a sample of our auth code:


const rcsdk = new SDK({

  server: RINGCENTRAL_SERVER,

  clientId: RINGCENTRAL_CLIENTID,

  clientSecret: RINGCENTRAL_CLIENTSECRET,

});





const platform = rcsdk.platform();





platform

  .login({

    jwt: JWT,

  })

  .then(async function (resp) {

    return resp.json();

  })

  .then((r) => console.log("login response", r));


Is this sufficient to maintain an active session until the JWT is set to expire? Or, do we need to be managing the login status more manually?

To get the token and return it, you have to use the await keyword 

platform

  .login({

    jwt: JWT,

  })

  .then(async function (resp) {

    return await resp.json();

  })

  .then((r) => console.log("login response", r));

Reply


Terms & ConditionsCookie settings