from time to time it happens that a created S2S OAuth token becomes invalid and cannot be used anymore for API consumption before the 3600 seconds of validity are over.
Unfortunately I could not reproduce the problem yet when I was trying to in order to restrict it to a certain behavior of our API clients . But from a gut feeling it happens after this token has been used for creating/deleting users and/or creating/deleting meetings.
Does anyone have an idea what could be the problem, or even similar experiences?
Do you have multiple instances of your application running at the same time (e.g. in a clustered environment)? You might be running into the undocumented “feature” where the previous OAuth token is invalidated when you request a new one.