Connector Authentication Expiration

Good afternoon,

I am working with a client to complete an integration between Tulip and MS Sharepoint, specifically to pull data from an Excel into a Tulip app.

The connector works as intended (after authenticating through Oauth2 with a service account), for a short period of time, but it will revert back after a couple of hours and throw up an error indicating that the user does not have permissions to access the Sharepoint site, which requires the connector to be authenticated by the service account owner again. The cert/secret we have created on Entra for this application are set to expire yearly so we are sure that this is not caused by expiring certs/secrets.

I have replicated the integration on our own Microsoft Entra portal and this error does not occur - i.e the connector remains authenticated after completing the auth process just once. The only obvious differences we can see between our clients Microsoft environment and our own is that the client usually requires users to sign in using MFA, though an exception has been granted to the service account being used to authenticate the connector (as it is not realistic to have a service account with a phone number that is not actually tied to a real employee).

We are in the process of trying to diagnose what is causing the connector to “de-authenticate” after a short period of time, but I wanted to run this by the community to see if anyone had any experience with similar issues with connector authentication being broken after a period of time?

Please let me know if there is any info I can provide to help illuminate things further!

Thanks

Hi @surajp - have you tried implementing refresh tokens here? Quote from “OAuth2.0 Configuration and Technical Details”