Token being invalidated when config TokenTimeout is -1 (no expiration)ww

Gabriel.Pacheco47

Hi there,

 

I have an API that does communicate with D2L API in the background to do some scheduled and user-requested actions. Therefore OAuth does not work for me as D2L does not support OAuth client credentials type, which would allow a nom-browser environment to request OAuth credentials. (https://community.brightspace.com/s/question/0D50A00000HKDPpSAP/is-oauth-client-credentials-grant-type-supported)

 

With that said I had to generate API keys through https://apitesttool.desire2learnvalence.com/ and that worked fine for the last 6 months or so.

 

Today the system was raising some issues and checking them closely I saw a "403 - Invalid token" error coming from D2L API requests.

 

This, clearly indicates that my token has expired. However, on my understanding, I could generate tokens that do not expire if the variable 'Security.Api.TokenTimeout' on 'Config Variable Browser' was -1, which I checked on the UI and it's.

 

Is my understanding correct? Does the expiration of this token generated at 'apitesttool' is controlled by the 'Security.Api.TokenTimeout' or any other?

 

 

Any help would be appreciated.

 

Gabriel