Create E-Mail Listener integration ability using OAuth that does not require a refresh token

Since Microsoft has declared the legacy Exchange integration capability out of support everyone was forced to move to OAuth technology. Within Maximo IBM has provided a new ability to support this OAuth connection protocol within the E-Mail Listener Process. This OAuth protocol replaces POP3S and IMAPS. The new OAuth protocol however forces to be configured using a Refresh Token mechanism. As explained by Microsoft on the below pages, this refresh token mechanism requires regular maintenance every 90 days due to expiring refresh tokens. Within every 3 months a new token needs to be generated and this new token needs to be configured in the E-Mail Listener configuration within Maximo. Microsoft describes that the lifetime expiration cannot be influenced/configured. More info: https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-configurable-token-lifetimes#token-lifetime-policies-for-refresh-tokens-and-session-tokens This setup is not desired as the E-mail Listener is a key component/feature within our Service Desk processes for the services delivered to our customers. The risk of having a breakdown in the e-mail llistener process is not desired. This could result in SLA breaches and even in penalty's if contract obligations are not being met. Therefore it is not desired to introduce additional maintenance to keep this E-Mail Listener process running. We truly wonder why IBM implemented a solution using a refresh token as this requires the administrators to generate new tokens every 90 months and requires a mail listener configuration update. The need of refreshing the token and updating the configuration introduces an additional maintenance task that we did not have before. Besides it is an additional business risk which is not acceptable in our point of view. There are additional possibilities of setting up OAuth integrations that do not require a refresh token. You could use a more standardized mechanism that uses username/password as well. This allows for easier maintenance and less frequent password updates. Consider the potential business risk and the additional maintenance costs this mechanism introduces that we did not have before with the old Exchange connections.