Unfortuntately, neither of the links actually explains what needs to be registered where nor (presumably) how to obtain the 'client-id' token used in the examples on the page.
There is lots of stuff about setting up GCP accounts/projects, but nothing about getting a client-id. Additionally there is lots of documentation on how to use third party apps with the IMAP interface, but nothing (that I can find) on how authentication is now meant to work with IMAP on gmail for a simple program.
Isn't the withdrawal of an authentication mechanism quite a serious security event as it severely hits the availability (as in the mnemonic of Confidentiality, Integrity, Availability for Security) of the service?
The wiki includes the comment (on https://github.com/google/gmail-oauth2-tools/wiki/OAuth2DotPyRunThrough): "To use OAuth2, you must have registered your application through the Google APIs Console. Registration is explained in Using OAuth 2.0 to Access Google APIs."
Unfortuntately, neither of the links actually explains what needs to be registered where nor (presumably) how to obtain the 'client-id' token used in the examples on the page.
There is lots of stuff about setting up GCP accounts/projects, but nothing about getting a client-id. Additionally there is lots of documentation on how to use third party apps with the IMAP interface, but nothing (that I can find) on how authentication is now meant to work with IMAP on gmail for a simple program.
Isn't the withdrawal of an authentication mechanism quite a serious security event as it severely hits the availability (as in the mnemonic of Confidentiality, Integrity, Availability for Security) of the service?