[EPIC] Oauth Support in Platform

[sherifnada]

MVP

UI

• UI: when displaying an oauth connector's spec, hide any oauth init parameters from the user #5644
• UI: integrate with oauth endpoints #5646
• UI: when displaying an oauth connector's spec, show an "authorize" button to initiate the oauth flow #5645
• UI/Webserver: Expose an endpoint to which a user should be redirected after granting Oauth consent #5770
• Only hide Oauth inputs if UI is running for cloud #6027
• oauth: finalize UI mockups #5651

Server

• verify that a single developer app can have multiple oauth refresh tokens for the same user #5643
• Server: Add oauth java module #5641
• Server: inject instance-wide variables into connector configs sent through web backend #5638
• Server: add the ability to bind instance-wide oauth parameters to a connector definition ID #5637
• Server: declare an endpoint to get a refresh token given an auth code and a connector definition ID #5640
• Server: create an endpoint to redirect user to oauth consent screen given a connector definition ID #5639
• Agree on contract with UI about oauth parameters #5647
• Add test to validate that oauth secrets are not exposed in export process #5895
• Server: Support Google Ads Oauth #5771
• Server: Support Google Analytics Oauth #5772
• Server: Support Google Search Console Oauth #5773
• Server: Support FB Marketing Oauth #5774
• Add API endpoints to write instance-wide secrets #5920
• OSS oauth demo #5919
• Return Google oauth parameters to the UI in the same format as they would be structured in the UI config #6026

Cloud Server

• Cloud Server: Set instance-wide secrets for Google Ads & Google Analytics #5775
• Cloud: Setup bootstrap script for adding instancewide variables on server startup #6024
• Upgrade cloud to 0.29.18 to pickup backend changes #6102
• Guard instancewide endpoints with super admin permissions #6094
• Demo using curl commands on cloud backend #6103
• Upgrade to pickup UI changes #6104

Protocol/Connectors

• Protocol: add references to oauth parameters in connector spec #5632
• Source FB marketing: Declare oauth parameters #5633
• Declare oauth parameters in google sources #5634

After all cloud server work is done

• OAuth E2E demo on prod cloud #6112
• Apply for complete public access for google analytics #6109
• Apply for complete public access for google ads #6110
• Apply for complete public access for google search console #7037
• Apply for complete public access for facebook marketing #6111
• Apply for complete public access for salesforce

Ideally-MVP-but-not-strictly-necessary

• Document how to declare oauth parameters in a connector in the connector specification reference #5636
• Source Salesforce: declare oauth parameters in spec #5635
• OAuth implementation testing spec #4982
• https://github.com/airbytehq/airbyte-internal-issues/issues/239
• airbytehq/airbyte-internal-issues#243

Post-MVP

• Document end-to-end how to add an oauth connector integrated in the UI #5648
• Source delta lake: support oauth #5141

[ChristopheDuong]

Should we also add this ticket? https://github.com/airbytehq/airbyte-internal-issues/issues/243