OAUth2.0 email setup without imap/pop

dnielso5

Hello,

I'm hoping someone can help me understand OAUth2.0 email configuration.

In the settings you need to select IMAP or POP as your connection, and then you can select OAUth2.0, is the OAUth2.0 just the way in which you authenticate? Our datacenter is telling me they wont set this up as you still are connection over IMAP/POP and they require more secure methods such as SMTP or "Modern Auth (also referred to as OAUth2.0) connection" according to them.

Is that not what is being set up? and if not is there any way to add that functionality?

Thank you.

ramrajone

dnielso5
here is official documentation about it: https://docs.osticket.com/en/latest/Guides/OAuth2%20Guide.html

dnielso5

ramrajone

so I'm just trying to get a clear cut answer, does that remove the need for IMAP/POP?

"OAuth2 Authorization allows emails the ability to authenticate against a mail server using the OAuth2 protocol." this line makes me think that no, you do NOT need to select IMAP/POP.

ramrajone

dnielso5
IMAP and OAuth2.0 are two different things that can be used together for accessing emails
IMAP (Internet Message Access Protocol): This is a protocol for accessing email stored on a server.
OAuth2.0 (Open Authorization): This is an authorization framework that allows applications to obtain limited access to user accounts on an HTTP service.

You are selecting IMAP, but using the Modern Auth (OAUth2.0)

Your data center seems to be under the impression that OAUth2.0 replaces the need for secure protocols like SMTP. This is not accurate. OAUth2.0 is for authentication, while IMAP/POP or SMTP are for email actions (retrieving or sending)

dnielso5

Thank you, because they didn't want to use imap or pop is there a way to add in smtp?

ramrajone

dnielso5

IMAP is for retrieving and managing emails, while SMTP is for sending emails. They work together to facilitate the exchange of emails between users.

KevinTheJedi

dnielso5

Exactly as ramrajone said, IMAP (RFC 9051) and POP3 (RFC 1939) are protocols used to fetch emails from a mailserver. SMTP (RFC 5321) is a protocol to send emails from a mailserver. Modern Authentication (OAuth2) (RFC 6749) is an authorization mechanism that uses access tokens that have specific permissions allowed. Our system allows using Modern Authentication (OAuth2) in tandem with IMAP or POP3 to fetch emails to create Tickets and append new messages to existing Tickets. Our system also allows using Modern Authentication (OAuth2) in tandem with SMTP to send emails like alerts, agent replies, etc.

If your host doesn't allow the IMAP/POP3 protocols (or doesn’t understand basic email and authorization concepts) you can look into Email Piping (local or remote) or processing emails via the Ticket API.

Cheers.

dnielso5

Ok, i found out what i was missing, our security department disabled IMAP and POP and we must use Exchange Web Service for mail connections.

KevinTheJedi

dnielso5

Since they only allow EWS (not supported in osTicket) you’ll have to look into the below:

… you can look into Email Piping (local or remote) or processing emails via the Ticket API.

Cheers.