Does not display lists needs access token? about mmm-microsofttodo HOT 7 CLOSED

@dvnnyburgx The issue seems to be with generating the access token. I suggest to try again the whole installation in the Azure portal and update the oauth* configuration parameters accordingly. If you like you can also contact me on twitter with a direct message (https://twitter.com/thobach) and I'll let you know my email address to send me screenshots of the Azure portal configuration.

from mmm-microsofttodo.

Hello, I have the same problem after the MM ran for months without any problems.

from mmm-microsofttodo.

It looks like I have a similar problem after months of working perfectly. Error message in MagicMirror was that user could not be authenticated due to account expiration. After login in Azure/Microsoftonline I see a message:
The logged in user is not authorised to fetch tokens for extension ‘Microsoft_AAD_IAM’ because user is not a member of tenant.

Any ideas to solve this issue (it used to worked like a charm ;-)

from mmm-microsofttodo.

Same for me here, used to work still few days ago, now after fresh install I also get a bad request on login with my tokens:

18.05.2022 21:33.58.198] [ERROR] Response {
  size: 0,
  timeout: 0,
  [Symbol(Body internals)]: {
    body: PassThrough {
      _readableState: [ReadableState],
      _events: [Object: null prototype],
      _eventsCount: 2,
      _maxListeners: undefined,
      _writableState: [WritableState],
      allowHalfOpen: true,
      [Symbol(kCapture)]: false,
      [Symbol(kCallback)]: null
    },
    disturbed: false,
    error: null
  },
  [Symbol(Response internals)]: {
    url: 'https://login.microsoftonline.com/common/oauth2/v2.0/token',
    status: 400,
    statusText: 'Bad Request',
    headers: Headers { [Symbol(map)]: [Object: null prototype] },
    counter: 0
  }
}

from mmm-microsofttodo.

What worked for me was going through the azure process again. Following the steps in the tutorial from Client Secret Key Generation till the end. I deleted old secret key first but might work with two as well.

from mmm-microsofttodo.

@mirko3000 @dvnnyburgx Does the workaround from @mithrandir80 work for you as well?

What worked for me was going through the azure process again. Following the steps in the tutorial from Client Secret Key Generation till the end. I deleted old secret key first but might work with two as well.

You could also check first if the secret at this screen is not expired.

from mmm-microsofttodo.

@thobach: yes actually that solved my issue here. Maybe because my old client secret was valid for more than 2 years (not allowed anymore)? Anyhow, working now again, thanks all!

from mmm-microsofttodo.