We have a Exchange online environment where we storage and manage our emailadresses.
We have a shared support mailbox that we want to connect to JSM so the emails automatically convert to a JSM-issue.
We allready tried the option in this article and got it working: https://support.atlassian.com/jira-cloud-administration/docs/create-issues-and-comments-from-email/
However, in this case, one specific user needs to login / connect using MFA all the time (or disable MFA and only use password, but thats agains our policy), so thats not working on the long term.
Is there a cloud configuration, simular to the Data center option described here: https://confluence.atlassian.com/adminjiraserver/configure-an-outgoing-link-1115659066.html
For JSM you should be able to using this documentation
(the one you linked is using the email handler)
Either way, using OAuth2 the user only needs to connect once and authorize the permissions. After that the OAuth2 link should take over.
I would still suggest using a generic/service account otherwise if the authorizing user goes away or changes their password the authorization has to be redone too.
Hi Dirk,
Thanks for the reaction. So, if i got it right, we can proceed to install the emailadress using 2FA and we only need to do this once?
We are aware of the consequence if the user leaves the organisation. However, we are not allowed to use generic accounts.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That would indeed be the case, the user who has access to the mailbox will need to run the MFA when performing the OAuth2 setup.
Once done the flow will rely on the refresh token and you should be good until the password is changed or the user is disabled.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.