What account to use to "Authorize Email Account Access" (OAUTH2)

[Patrik Samuel T]

Hi,

we are currently setting up Outlook email accounts using OAUTH2. I have followed steps in KB0816072, but the authorization part is not completelly clear to me and it could provide more detais and screenshots.

KB says I should not use my account, so what account should I use? When I open (in-private) that URL from "Authorize Email Account Access" button, Outlook login page appears, as we use SSO with Azure. If I use credentials for the email account, I am trying to setup, I am able to login, but that email is not associated with any user in ServiceNow, hence I cannot proceed to finish the authorization.

KB also mentions side_door.do and local login, but what account to use? Should I use the build in System Administrator account instead?

Thanks for clarification

Patrik

[Tony Chatfield1]

Hi, I believe that it is best practice to create a user\integration account specific to every separate integration. 

Looking at the KB article you linked, the explanation seems to indicate that a specific integration account should be created at the Outlook side and that you should then use this accounts credentials for authentication.

[Ninette1]

Hi, did you find a solution for this problem, I have the same issue

[Patrik Samuel T]

Hi,

I did the authorization part from build-in "admin" account. I right click on the Authorize button, Copy url, paste it to in-private browser session, sign-in with email credentials (of the account I am authorizing).

I am using separate browsers/in-private session because we have SSO, so I do not want to mix session cookies for multiple accounts, as this sometimes has "weird" results.

Done this in 3 instances, total of like 6 accounts.

On our two pre-pro instaces, IMAP setup broke after a week and connection test started failing with weird error. I have to yet look into this, but setup on prod still rocks, weeks later.

Couldn't connect to host, port: outlook.office365.com, 993; timeout 20000; Using socket factory class com.glide.certificates.DBKeyStoreSocketFactory

Patrik

[MattS4]

Did you ever determine the cause of this error? We are getting it now in our DEV environment and can't seem to find the issue