-
-
Notifications
You must be signed in to change notification settings - Fork 814
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dev/core#2264 - Remove never-used IMAP_XOAUTH2 option value before it gets more confusing #19243
Conversation
(Standard links)
|
'auth' => $protocol === 'IMAP_XOAUTH2' ? 'XOAuth2' : 'Password', | ||
// In a simpler world: | ||
// 'auth' => 'Password', | ||
'auth' => 'Password', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@demeritcowboy won't this break the XOUATH2 integration? or am I confused by things here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See it is confusing! No because IMAP_XOAUTH2 is never used. Whether to use oauth2 with imap comes from the settings stored in a different place, via $mailSettings['auth']
below.
I also tested this with the same setup I had used for testing oauth2 before. Still seems to work.
This seems ok to me just noting that the oauth extension alters the mail settings here
|
@totten can you eyeball this one? |
@demeritcowboy Needs rebase |
bdc29c0
to
3d83912
Compare
This is a good idea. I did some Pushed up some tweaks to the message text. Merge on pass. |
Thanks! |
Overview
https://lab.civicrm.org/dev/core/-/issues/2264
Before we knew the full
wackinesssplendor of OAUTH2, there was an attempt to model it as its own protocol. This never worked so as the 5.23 release was going to press the as-yet-unreleased mail protocol option value was disabled, but left in the database.Now that (inbound) OAUTH2 is working using a different mechanism, remove this option value before it starts causing confusion.
Before
Confusing.
Backwards compatibility code exists that is almost certainly not being used.
After
Better.
If it happens to be used somehow, there's a message upon upgrade asking person to report what they are doing.
Technical Details
OAUTH2
Comments
Also #18902 (comment)